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/sagaaidev/mcp-ahrefs/test-apigit clone --depth 1 https://github.com/SAGAAIDEV/mcp-ahrefsWrote 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/sagaaidev/mcp-ahrefs/test-api)<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/test-api"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/test-api.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.00007 | $0.00542 |
| Opus 5 | $0.00003 | $0.00271 |
| Sonnet 5 | $0.00001 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
test-api 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 3d 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
I'll test the backend API using pytest, focusing on $ARGUMENTS.
Step 1: Analyze API Structure
First, let me understand the API structure:
Find API endpoints
!find . -name "*.py" -type f | xargs grep -l "@app|@router|@api" | grep -v pycache | head -20
Check existing tests
!find . -path "/test" -name "*.py" | grep -v pycache | head -20
Review test configuration
!test -f pytest.ini && cat pytest.ini || echo "No pytest.ini found" !test -f pyproject.toml && grep -A 10 "[tool.pytest" pyproject.toml || echo "No pytest config in pyproject.toml"
Step 2: Determine Test Scope
Based on the arguments and current changes, I'll focus on:
- Endpoint patterns to test
- Test types: unit, integration, or all
- Authentication requirements
- Data validation scenarios
Step 3: Create/Update Tests
I'll create appropriate test files based on the feature:
For new endpoints:
- Create test file in tests/integration/
- Write tests for all HTTP methods
- Include validation tests
- Add error handling tests
For modified endpoints:
- Update existing tests
- Add tests for new functionality
- Ensure backward compatibility
Step 4: Run Tests
Execute pytest with appropriate options:
!pytest -v # Verbose output
Run with coverage:
!pytest --cov=app --cov-report=term-missing
Run specific tests if needed:
!pytest -k "$ARGUMENTS" -v
Step 5: Analyze Results
I'll review:
- Test pass/fail status
- Coverage report
- Performance metrics
- Any unexpected failures
Common Test Scenarios
I can help test:
- CRUD Operations: Create, Read, Update, Delete endpoints
- Authentication: Token validation, permissions
- Validation: Request body validation, query parameters
- Error Handling: 4xx and 5xx responses
- Pagination: Limit/offset, cursor-based
- Filtering: Query parameters, search
- File Operations: Upload, download
- Async Endpoints: Background tasks, WebSockets
Let me begin analyzing your API...
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.
- 3d ago First seen · 77 lines · 7 tokens per session scan A 213f407ce5e2
test-api is a command published in the GitHub repository SAGAAIDEV/mcp-ahrefs (0 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 542 once invoked, about $0.0000 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-31.
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.
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.