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.
git clone --depth 1 https://github.com/mrlm-xyz/demo-claude-marketplaceWrote 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/mrlm-xyz/demo-claude-marketplace/audit)<a href="https://agentmods.dev/commands/mrlm-xyz/demo-claude-marketplace/audit"><img src="https://agentmods.dev/badge/commands/mrlm-xyz/demo-claude-marketplace/audit/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/mrlm-xyz/demo-claude-marketplace/audit"><img src="https://agentmods.dev/badge/commands/mrlm-xyz/demo-claude-marketplace/audit.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.00020 | $0.00278 |
| Opus 5 | $0.00010 | $0.00139 |
| Sonnet 5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
audit 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 12d 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
Audit Command
Conduct a thorough security audit of API implementation to identify vulnerabilities and recommend mitigations.
Scope
This command performs security analysis covering:
- Authentication mechanisms (OAuth, JWT, API keys)
- Authorization and access control logic
- Input validation and sanitization
- Injection vulnerabilities (SQL, NoSQL, command)
- Sensitive data exposure and leakage
- Rate limiting and DoS protection
- Security headers and CORS configuration
- Dependency vulnerabilities
Execution Flow
- Review API specification and implementation
- Analyze authentication and session management
- Check authorization logic and access controls
- Test input validation and sanitization
- Scan for injection vulnerabilities
- Review error handling and information disclosure
- Check rate limiting and quota enforcement
- Verify encryption for sensitive data
- Document findings with severity levels
- Recommend specific mitigations with examples
Constraints
- Use api-guardian security skills for analysis
- Follow OWASP Top 10 methodology
- Provide severity ratings (Critical, High, Medium, Low)
- Include proof of concept for findings
- Recommend practical mitigations
- Consider both design and implementation issues
- Document assumptions and scope limitations
- Prioritize findings by risk and impact
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.
- 12d ago First seen · 44 lines · 20 tokens per session scan A a5dfcc40cda5
audit is a command published in the GitHub repository mrlm-xyz/demo-claude-marketplace (34 stars, last pushed 9d ago), licensed Apache-2.0. It adds 20 tokens to every session and 278 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
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.