Skip to main content

AI integrations for MostafaKady.com

This document defines the provider roles, setup steps, cost limits and safety rules for AI-assisted work on this repository.

Non-negotiable cost policy

  • No paid subscriptions, paid API calls, prepaid credits, paid trials, auto top-ups or services that can silently switch to paid usage.
  • Do not attach a billing account to a provider project used by an integration intended to remain free.
  • A free web chat plan is not the same as free API access.
  • If a provider changes its free-tier terms, disable the integration until the new terms are reviewed.
  • Never put credentials in source files, workflow YAML, pull-request text, commits or logs. Use GitHub Actions repository secrets.
  • Never allow an AI review to merge or deploy code by itself.

Current provider assessment (checked 2026-11-08)

Provider Free integration route Role Decision
Google Gemini Gemini Developer API has a free tier for selected models; free-tier content may be used to improve Google products Opt-in PR diff review Implemented as a manually invoked workflow; requires a user-created free-tier API key
Manus Free plan includes limited daily credits and GitHub connector access Repository exploration, task execution and draft PRs Connect through Manus UI; no repository secret or API key required
Claude Claude Code GitHub Action requires a paid Claude subscription OAuth token or billable API credentials; API uses prepaid credits Deep code review and implementation Do not enable in the zero-cost workflow unless a genuinely included subscription entitlement is confirmed
Perplexity Consumer free search is separate from the API; API is pay-as-you-go and has no complimentary API credits Research and source discovery Use its free web interface manually; do not add API automation

Provider terms and quotas can change. Confirm the linked official pricing pages before enabling a new integration.

1. Gemini: optional pull-request review

The workflow .github/workflows/gemini-pr-review.yml is deliberately opt-in. It does not run on every PR and cannot modify repository files.

Setup

  1. Open Google AI Studio.
  2. Create an API key in a project that remains on the Gemini API Free Tier. Do not link a billing account or upgrade the project.
  3. In GitHub, open this repository → Settings → Secrets and variables → Actions → New repository secret.
  4. Set the secret name to GEMINI_API_KEY and paste the key as its value.
  5. Open a pull request in this repository and add the exact comment /gemini-review as the repository owner.

The workflow sends only the pull-request diff (capped at 30,000 characters) to Gemini. It posts an advisory review comment. It does not check out or execute PR code, push commits, edit files, merge, or deploy.

Data handling warning

Google’s published Gemini API Free Tier terms state that submitted content may be used to improve Google products. Do not use this workflow on diffs containing secrets, private personal data, confidential third-party material or unpublished sensitive research. Remove such material before invoking the review. The workflow is manual to keep data sharing deliberate.

If the API key’s project is upgraded to a paid tier, stop using the workflow until the free-only requirement can be re-established.

2. Manus: connect GitHub from Manus

Manus provides a built-in GitHub connector. Its Free plan is limited by credits, concurrency and available agent features; it is not unlimited automation.

  1. Sign in to Manus.
  2. Open Connectors and choose GitHub.
  3. Authorize GitHub and select only mostafa-kadi/mostafakady-website.
  4. Ask Manus to inspect the repository first. Do not initially grant access to unrelated repositories.
  5. Instruct it to work on a dedicated branch and open a pull request; do not permit direct pushes to main or production deployment.

Suggested first task:

Inspect mostafa-kadi/mostafakady-website. Explain the Quarto structure, GitHub Actions workflows, Cloudflare deployment path and current open pull requests. Do not modify files. Report conflicts, security risks, outdated configuration and opportunities for free AI-assisted automation.

Only enable Manus-triggered PR automation after its behavior and repository permissions have been reviewed. Keep auto-merge disabled for Manus-generated changes.

3. Claude: subscription/API distinction

Claude’s consumer chat, Claude Code and Anthropic API have separate entitlements. The official Claude Code GitHub Action requires either an Anthropic API key (prepaid/billed usage) or a Claude Code OAuth token associated with an eligible Pro/Max plan. Do not create an API key or add payment details for this project under the free-only policy.

If an eligible Claude subscription is already available, verify that its terms explicitly include Claude Code and that usage is within the included allowance before considering a manual, non-automated workflow. Do not assume a free Claude chat account includes GitHub Actions access.

4. Perplexity: research only

Perplexity’s free consumer search can be used manually for research. Its API Platform is billed separately on a pay-as-you-go basis and does not include complimentary API credits. No Perplexity API key or automated API workflow should be added under the free-only policy.

Review and deployment boundaries

  • GitHub Actions remains responsible for deterministic build, link, accessibility and Lighthouse checks.
  • AI reviews are advisory and must never replace tests or human review.
  • AI-generated changes must be isolated on a branch and proposed through a PR.
  • Production deployment remains exclusively in .github/workflows/publish.yml after an approved merge to main.
  • Never expose CLOUDFLARE_API_TOKEN, CLOUDFLARE_WORKERS_API_TOKEN, OAuth secrets or other deployment credentials to AI workflows.