Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/el-feo/ai-context/install-reviewgit clone --depth 1 https://github.com/el-feo/ai-contextWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/el-feo/ai-context/install-review)<a href="https://agentmods.dev/commands/el-feo/ai-context/install-review"><img src="https://agentmods.dev/badge/commands/el-feo/ai-context/install-review.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00015 | $0.00539 |
| Opus 5 | $0.00008 | $0.00269 |
| Sonnet 5 | $0.00003 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
install-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Install the Fowler refactoring review workflow into this repository. The
workflow runs claude-code-action on every opened/reopened PR (and on
/fowler PR comments), installs the fowler plugin from the jebs-dev-tools
marketplace into the CI runner, and delivers a code-smell diagnosis as inline
PR comments plus one summary comment with a prioritized refactoring order.
The generic template lives at ${CLAUDE_PLUGIN_ROOT}/templates/fowler-review.yml.
Follow these steps:
-
Verify the repo. Confirm the current directory is a git repository with a GitHub remote (
git remote -v). If not, stop and explain that the workflow only works on GitHub-hosted repos. -
Check for an existing install. If
.github/workflows/fowler-review.ymlalready exists, show the user how it differs from the template and ask before overwriting. -
Copy the template to
.github/workflows/fowler-review.yml(create the directory if needed). -
Scope the review (optional). If the user passed path globs as arguments, or asks to limit the review to part of the codebase:
- Add a
paths:filter under thepull_requesttrigger with those globs (replace the commented example). - Update the
Scope:paragraph in the prompt to say the review covers ONLY changed files matching those paths and ignores changes elsewhere.
If no scope was given, leave the template as-is — it reviews all changed files in the PR.
- Add a
-
Verify the secret. Run
gh secret listand check forCLAUDE_CODE_OAUTH_TOKEN. If it's missing, tell the user to create one:claude setup-token # generates an OAuth token (requires a Claude subscription) gh secret set CLAUDE_CODE_OAUTH_TOKEN -
Summarize. Tell the user: the workflow file installed, how it triggers (auto on PR open/reopen;
/fowlercomment from an owner/member/collaborator for a re-review), any scoping applied, and whether the secret is in place. Offer to commit the workflow file — but do not commit without their say-so.
$ARGUMENTS
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 51 lines · 15 tokens per session scan A 7a1054fd4560
install-review is a command published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 539 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
actions
Command "actions" from openclaw/crabbox, covering actions, subcommands, hydrate, register and dispatch.
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.