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 marconae/speq-skill --skill speq-auditgit clone --depth 1 https://github.com/marconae/speq-skillWrote 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/marconae/speq-skill/speq-audit)<a href="https://agentmods.dev/skills/marconae/speq-skill/speq-audit"><img src="https://agentmods.dev/badge/skills/marconae/speq-skill/speq-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/marconae/speq-skill/speq-audit"><img src="https://agentmods.dev/badge/skills/marconae/speq-skill/speq-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00053 | $0.02193 |
| Opus 5.5 | $0.00021 | $0.00877 |
| Sonnet 5.5 | $0.00011 | $0.00439 |
| Haiku 4.5 | $0.00005 | $0.00219 |
Grade A, and why
speq-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 today.
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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Auditor (Orchestrator)
Thin orchestrator. It runs read-only health checks over a speq project, delegates the mission ↔ spec-library sync check to audit-agent, judges the ADRs itself, prints a summary, and offers to fix each finding. Always ask before a fix.
Required Skills (for the orchestrator)
Invoke before starting:
/speq-cli— spec discovery and thevalidatecommands/speq-writing-guardrails— prose style for the summary
Each check in references/checks.md names the skill that owns its rules. Invoke that skill instead of working from memory.
The audit-agent sub-agent invokes /speq-cli itself. Read references/checks.md for the per-check detection recipes, thresholds, and remediation procedures.
Workflow
Phase 0: Load Project Hook (orchestrator)
Check for .speq/audit-hook.md in the repo root.
- Present: read it. Announce "Loaded project hook: .speq/audit-hook.md". Its content is authoritative: it can add to, change, or override any part of this workflow. If the hook conflicts with this workflow, the hook wins.
- Absent: continue normally, no mention.
Note it (not its full content) as a Project Hook: line in each sub-agent brief below.
Phase 1: Preconditions (orchestrator)
Check: specs/ directory exists?
├─ Yes → proceed
└─ No → STOP: "No spec library found. Run /speq-mission to bootstrap."
Phase 2: Run checks (orchestrator, READ-ONLY)
Run every check in references/checks.md, recording a ✓ / ✗ / ⚠ and a one-line detail for each. The Serena check records ℹ (hint) instead of ⚠. A hint is not a finding, so it never counts toward N findings and never gets a remediation. Modify nothing in this phase. The checks:
Layout
- Spec structure — every
spec.mdis atspecs/<domain>/<feature>/spec.md - Feature specs —
speq feature validate - Library thresholds — scenarios per spec, features per domain
Decisions
4. Decision log — old specs/decision-log.md vs specs/_decision/; speq decision-log validate
5. ADR review — judged by the orchestrator (Phase 3b)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · -11 lines · -27 tokens per session 3b4d4d67732d
- 18d ago Changed · -3 lines ef169523c3f3
- 21d ago Changed · +7 lines b4855e4a7cfc
- 1mo ago Changed · +37 lines · +3 tokens per session 0e7c741722ab
- 1mo ago Changed c4bc903891f9
- 1mo ago First seen · 143 lines · 77 tokens per session scan A 471f46506f87
speq-audit is a skill published in the GitHub repository marconae/speq-skill (55 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 2,193 once invoked, about $0.0002 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-30.
Other skills, from other repositories
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
backprop
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.
check
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec.…
ase-code-lint
Lint source code for potential code quality problems. Use when the user wants to "lint" or "check" source code.
ase-code-edit
Edit Source Code: Use when the user wants to "edit" the code base in one shot from a query or a bare analyzer issue id like "P1", fusing crafting, refactoring, and resolving with optional grilling, verification, looping, and Git worktree isolation.
critical-review
4-phase adversarial review protocol: pre-flight analysis, adversarial execution check, self-correction loop, and [VALIDATION] report.