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 skills add instantcms-dev/instantcms-mcp --skill instantcms-auditgit clone --depth 1 https://github.com/instantcms-dev/instantcms-mcpWrote 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/skills/instantcms-dev/instantcms-mcp/instantcms-audit)<a href="https://agentmods.dev/skills/instantcms-dev/instantcms-mcp/instantcms-audit"><img src="https://agentmods.dev/badge/skills/instantcms-dev/instantcms-mcp/instantcms-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/skills/instantcms-dev/instantcms-mcp/instantcms-audit"><img src="https://agentmods.dev/badge/skills/instantcms-dev/instantcms-mcp/instantcms-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.00033 | $0.00155 |
| Opus 5.5 | $0.00013 | $0.00062 |
| Sonnet 5.5 | $0.00007 | $0.00031 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
instantcms-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 1mo 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
InstantCMS audit
Identify the artifact type and validate its complete file map with the project MCP server. Report stable diagnostic codes and exact paths.
Check generated-format syntax with real parsers where available: PHP lint, XML parsing, INI parsing, YAML parsing, and archive path inspection. Review user-controlled output for context-appropriate escaping and reject traversal paths.
Separate confirmed defects from compatibility risks and optional improvements. Do not modify files during a review unless the user requested fixes.
For release archives, use the installed instantcms-packager skill rather than recreating packaging rules.
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.
- 1mo ago First seen · 15 lines · 33 tokens per session scan A 25c016c46f4b
instantcms-audit is a skill published in the GitHub repository instantcms-dev/instantcms-mcp (11 stars, last pushed 9d ago), licensed MIT. It adds 33 tokens to every session and 155 once invoked, about $0.0001 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 skills, from other repositories
review
Review one pull request for real bugs, regressions, and convention violations. Enumerate candidate issues across the whole diff, verify each against the code, then return structured line-anchored findings and a verdict. Read-only on GitHub; the orchestrator posts the review.
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
code-review
Use when code has been written and needs validation before committing, or when the user asks for a code review or security check.
auto-review
Use this skill to configure and understand the built-in auto-review plugin (wstack-auto-review) that fires automated code review subagents on every code change during a session. Triggers: user says "auto review", "otomatik review", "auto code review", "her değişiklikte review", "/auto-review".
code-review
Use this skill when asked to review code changes — a pull request, a branch, a commit range, or the current diff — for correctness, security, and maintainability before they merge. Triggers: user says "review", "code review", "review this PR", "review my changes", "look over the diff", "is this ready to merge", "PR…
codex-adversarial-review
Use this skill to conduct aggressive, adversarial code reviews on git changes, branches, or PRs to detect critical edge cases, race conditions, security holes, and data loss risks. Triggers: user mentions "adversarial review", "break the code", "find vulnerabilities", "security audit PR", "race condition check", "ship…