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/issuegit 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.01786 |
| Opus 5 | $0.00000 | $0.00893 |
| Sonnet 5 | $0.00000 | $0.00357 |
| Haiku 4.5 | $0.00000 | $0.00179 |
Grade A, and why
issue 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Please analyze and fix the Github issue: $ARGUMENTS.
Follow these steps for comprehensive issue resolution:
PLAN
-
Get issue details:
gh issue view $ISSUE_NUMBER -
Understand the problem described in the issue:
- Read the issue description carefully
- Check any attached screenshots or logs
- Understand the expected vs actual behavior
- Identify the scope (bug fix vs feature implementation)
-
Ask clarifying questions if necessary in issue comments
-
Research prior art and context:
- Search existing documentation in
docs/for related information - Search PRs to see if you can find history on this issue:
gh pr list --search "keyword from issue" - Search the codebase for relevant files using Grep/Glob tools
- Check if similar issues have been resolved before
- Search existing documentation in
-
Break down the work using TodoWrite tool:
- Identify all components that need changes
- Plan implementation steps
- Consider testing requirements
- Plan documentation updates
-
Create documentation plan:
- Determine which
docs/files need updates - Plan new documentation if implementing features
- Consider updating:
docs/GETTING_STARTED.mdfor user-facing featuresCONTRIBUTING.mdfor development changesdocs/ARCHITECTURE.mdfor architectural changesdocs/TECHNICAL_REFERENCE.mdfor technical implementations- Create issue-specific docs in
docs/with appropriate categorization
- Determine which
PRE-TEST VALIDATION
-
Switch to main branch and create new branch for the issue:
# Ensure you're starting from the latest main branch git checkout main git pull origin main # Create and switch to new feature branch git checkout -b issue-$ISSUE_NUMBER-brief-descriptionImportant: Always start from main to ensure your changes are based on the latest codebase and avoid merge conflicts.
-
Run the full test suite to ensure clean environment:
pnpm run check # Lint and format check pnpm run test # Unit tests pnpm run test:coverage # Coverage report pnpm run test:e2e # End-to-end tests (if applicable)
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 · 248 lines · 0 tokens per session scan A 9c1da3fa7783
issue 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,786 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.