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/istarwyh/mcpadvisor/pull-requestgit clone --depth 1 https://github.com/istarwyh/mcpadvisorWhat 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.00000 | $0.01171 |
| Opus 5 | $0.00000 | $0.00585 |
| Sonnet 5 | $0.00000 | $0.00234 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade A, and why
pull-request 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Please analyze and fix the Github pull request: $ARGUMENTS.
Follow these steps for comprehensive PR review and fixing:
PLAN
-
Switch to PR branch first:
gh pr checkout $PR_NUMBERThis ensures you're working on the correct branch for the PR.
Important Branch Management:
- The PR branch should already be based on main when created
- If you need to sync with latest main (e.g., for conflicts or outdated base):
# Update your local main first git checkout main git pull origin main # Switch back to PR branch and rebase on main gh pr checkout $PR_NUMBER git rebase main # If there are conflicts, resolve them and continue: # git add . # git rebase --continue -
Use
gh pr view $PR_NUMBERto get the PR details and description -
Use
gh pr view $PR_NUMBER --json reviews,commentsto get review comments and feedback -
Use
gh api repos/:owner/:repo/pulls/$PR_NUMBER/commentsto get detailed code review comments -
Understand all the feedback and suggestions from reviewers
-
Ask clarifying questions if any feedback is unclear
-
Analyze the codebase context:
- Search for related files mentioned in the review
- Understand the code patterns and conventions
- Check existing tests that might be affected
-
Break down all review feedback into manageable tasks using TodoWrite tool
-
Prioritize fixes: Critical > Major > Minor issues
PRE-TEST VALIDATION
- Run the full test suite to understand current state:
pnpm run check # Lint and format check pnpm run test # Unit tests pnpm run test:e2e # End-to-end tests (if applicable) - Document any existing test failures before making changes
- Ensure you understand which tests are related to the PR changes
SYSTEMATIC FIXING
For each review comment/suggestion:
- Mark todo as in_progress using TodoWrite tool
- Read the relevant files to understand context
- Implement the fix following project conventions:
- Follow naming conventions from CLAUDE.md
- Maintain code style consistency
- Use existing patterns and utilities
- Follow TypeScript best practices
- Verify the fix addresses the reviewer's concern
- Mark todo as completed using TodoWrite tool
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.
- 2d ago First seen · 167 lines · 0 tokens per session scan A 72df0a3b6d9f
pull-request is a command published in the GitHub repository istarwyh/mcpadvisor (89 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,171 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.