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/gustavo-meilus/superpipelinesWrote 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/gustavo-meilus/superpipelines/audit-steps)<a href="https://agentmods.dev/commands/gustavo-meilus/superpipelines/audit-steps"><img src="https://agentmods.dev/badge/commands/gustavo-meilus/superpipelines/audit-steps.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.1 | $0.00040 | $0.00536 |
| Opus 5 | $0.00020 | $0.00268 |
| Sonnet 5 | $0.00008 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
audit-steps 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 8d 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 Pipeline — Command Reference
Audits one or all pipelines against layout, frontmatter, topology, and runtime-safety standards. Produces a severity-classified report (SEV-0 to SEV-3) with cited evidence.
<operating_modes>
- Named Pipeline/Path →
FULLmode: Audits the complete bundle or specific files. --all→SCOPE-WIDEmode: Audits every pipeline across all available scopes. </operating_modes>
2. CLASSIFICATION & AUDIT
- Classify files into categories: subagent, internal skill, entry skill, reference, topology, or registry.
- Apply the full compliance matrix (see
compliance-matrix.md) across the four standard bands plus the resolver-consolidation criteria. - Execute topology graph rules, including edge consistency and cycle checks.
3. REPORTING
- Classify all findings by severity (SEV-0 to SEV-3).
- The auditor is read-only and never persists; the orchestrator owns persistence, in order:
- Ensure
<scope-root>/superpipelines/pipelines/{P}/audit/exists, creating it if missing (idempotent — no-op if present). This MUST precede the write so a fresh pipeline's first audit cannot fail on a missing directory. - Write the auditor's rendered report to
audit/latest.md. - Update the
last_audittimestamp inregistry.jsonper the auditor's instruction.
- Ensure
- Present the executive summary inline to the user. If the write fails after the directory is ensured, surface the error and the inline summary so findings are never lost.
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.
- 8d ago First seen · 42 lines · 40 tokens per session scan A afa87c48cdee
audit-steps is a command published in the GitHub repository gustavo-meilus/superpipelines (4 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 536 once invoked, about $0.0002 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
refactor
Refactor $ARGUMENTS following modern JavaScript/TypeScript best practices.
views
Create Django views with proper structure and best practices.
git-workflow
Manage Git workflows with best practices and common operations.
review-module.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects Ornek cikti.
bug-review.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure Ornek cikti.
services
Create Angular services for $ARGUMENTS following project conventions.