Borrowing it
Nothing to install: this file belongs to SAGAAIDEV/mcp-ahrefs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SAGAAIDEV/mcp-ahrefs/main/.claude/commands/test-api-subprocess.mdgit 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-subprocess)<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/test-api-subprocess"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/test-api-subprocess/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sagaaidev/mcp-ahrefs/test-api-subprocess"><img src="https://agentmods.dev/badge/commands/sagaaidev/mcp-ahrefs/test-api-subprocess.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00010 | $0.01050 |
| Opus 5.5 | $0.00004 | $0.00420 |
| Sonnet 5.5 | $0.00002 | $0.00210 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
test-api-subprocess 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 2mo 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'll execute comprehensive API testing using a Claude subprocess for autonomous test execution.
Step 1: Prepare Test Context
Gather API Information
!echo "Current branch: $(git branch --show-current)" !find . -name ".py" -path "/routers/" -o -path "/endpoints/" -o -path "/controllers/" | head -10 !grep -r "@app." . --include=".py" | head -5 || grep -r "@router." . --include="*.py" | head -5
Check Test Environment
!test -f requirements.txt && grep -E "(pytest|httpx|requests)" requirements.txt !test -f .env.test && echo "Test environment file found" || echo "No test environment file"
Step 2: Determine Test Scope
Based on the feature and acceptance criteria:
- API endpoints to test
- Integration points
- Authentication flows
- Data validation rules
- Error scenarios
Step 3: Launch Subprocess Testing
I'll execute the API tests using a Claude subprocess:
claude -p "You are testing a Python backend API. Your task is to:
1. Analyze the API structure in [PROJECT_PATH]
2. Test the following API workflow: [SPECIFIC_WORKFLOW_DESCRIPTION]
3. Create comprehensive test cases covering:
- Happy path scenarios
- Authentication and authorization
- Input validation (edge cases, invalid data)
- Error handling (4xx and 5xx responses)
- Data persistence and retrieval
- Integration with external services
4. For each endpoint test:
- All HTTP methods (GET, POST, PUT, DELETE)
- Query parameters and filters
- Pagination if applicable
- Request body variations
- Header requirements
5. Test data scenarios:
- Empty data sets
- Single items
- Large data sets
- Special characters and Unicode
- SQL injection attempts
- Maximum field lengths
6. Performance considerations:
- Response time for typical requests
- Behavior under concurrent requests
- Rate limiting if implemented
7. Create test files using pytest following the project structure
8. Run the tests and document results
9. Generate a coverage report
Use the following test patterns:
- Unit tests for business logic
- Integration tests for API endpoints
- Mock external services appropriately
- Use fixtures for test data setup
Focus on: [SPECIFIC_REQUIREMENTS]" --dangerously-skip-permissions
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.
- 2mo ago First seen · 162 lines · 10 tokens per session scan A 9d683e5b7b2c
test-api-subprocess is a command published in the GitHub repository SAGAAIDEV/mcp-ahrefs (0 stars, last pushed 1y ago), licensed MIT. It adds 10 tokens to every session and 1,050 once invoked, about $0.0000 per session on Opus 5.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
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.