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 Enovatr-Labs/SpecRoute --skill audit-artifactgit clone --depth 1 https://github.com/Enovatr-Labs/SpecRouteWrote 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/enovatr-labs/specroute/audit-artifact)<a href="https://agentmods.dev/skills/enovatr-labs/specroute/audit-artifact"><img src="https://agentmods.dev/badge/skills/enovatr-labs/specroute/audit-artifact/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/enovatr-labs/specroute/audit-artifact"><img src="https://agentmods.dev/badge/skills/enovatr-labs/specroute/audit-artifact.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.00087 | $0.00513 |
| Opus 5.5 | $0.00035 | $0.00205 |
| Sonnet 5.5 | $0.00017 | $0.00103 |
| Haiku 4.5 | $0.00009 | $0.00051 |
Grade A, and why
audit-artifact 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.
What it actually says
Audit Artifact
Use this skill when a user wants a guided readiness review of one SpecRoute artifact or a small related set of artifacts.
Inputs
Ask for any missing input before reviewing:
- Path - file or directory to audit.
- Artifact type - one of
prd,spec,agent,skill,command,hook,prompt,rule,runtime, orunknown. - Readiness target -
draft,review-ready, orimplementation-ready.
If the artifact type is omitted, infer it from the path and confirm the inference in the audit summary.
Workflow
- Read the artifact and its nearest README or template reference.
- Identify the applicable contract:
- PRDs need goals, non-goals, metrics, rollout, risks, dependencies, and acceptance criteria.
- Specs need stable requirement IDs, design coverage, task back-references, and validation steps.
- Agents and skills need valid frontmatter and clear boundaries.
- Commands, hooks, rules, and runtime layouts need vendor-native shape.
- Check for unresolved placeholders that are inappropriate for the readiness target.
- Check sanitization risk: private names, credentials, internal endpoints, customer data, or proprietary domain logic.
- Report findings in severity order with file references and concrete recommended fixes.
Output Shape
## Findings
- High: <blocking issue with path>
- Medium: <important non-blocking issue>
- Low: <cleanup>
## Ready?
<yes/no> for <readiness target>, with one sentence explaining why.
## Recommended Changes
- <smallest concrete edit>
Guardrails
- Do not rewrite the artifact unless the user explicitly asks for implementation.
- Do not invent missing business facts. Mark missing facts as required decisions.
- Treat placeholders as acceptable in templates and suspicious in approved examples.
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 · 58 lines · 87 tokens per session scan A 9de34787128a
audit-artifact is a skill published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 87 tokens to every session and 513 once invoked, about $0.0003 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
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
agent-code-review-swarm
Agent skill for code-review-swarm - invoke with $agent-code-review-swarm.
agent-swarm-pr
Agent skill for swarm-pr - invoke with $agent-swarm-pr.
agent-reviewer
Agent skill for reviewer - invoke with $agent-reviewer.
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agent-pr-manager
Agent skill for pr-manager - invoke with $agent-pr-manager.