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 agentmods add skills/gtrabanco/agentic-workflow/review-specnpx skills add gtrabanco/agentic-workflow --skill review-specgit clone --depth 1 https://github.com/gtrabanco/agentic-workflowWrote 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/gtrabanco/agentic-workflow/review-spec)<a href="https://agentmods.dev/skills/gtrabanco/agentic-workflow/review-spec"><img src="https://agentmods.dev/badge/skills/gtrabanco/agentic-workflow/review-spec.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.00077 | $0.01858 |
| Opus 5 | $0.00039 | $0.00929 |
| Sonnet 5 | $0.00015 | $0.00372 |
| Haiku 4.5 | $0.00008 | $0.00186 |
Grade A, and why
review-spec 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Spec
The Product gate. A designed SPEC's product half is reviewed here, by a
context that did not write it, before any engineering planning exists. Findings
and one verdict only — the repair belongs to design-feature.
Designed ≠ reviewed. `## Design status: designed` proves the author's own
closure check ran; this skill is what lets `plan-feature` trust the half.
Turn contract
Load and verify the canonical Turn contract (11 boxes) before ending every turn. This skill's additional boxes live only in OUTPUT.md. Missing reference → STOP. An about-to-end turn with an unchecked box is not done.
✓ Snapshot built from the exact bytes read at one revision (digest pasted)
✓ Every Product check of the selected stage row ticked or turned into a finding
✓ One verdict printed from the closed set, with the receipt block persisted —
write-then-report (`pre-execution-review`'s `POLICY.md` §8)
✓ Zero writes to any reviewed artifact (`SPEC.md`, `decisions.md`, roadmap,
`ACCEPTANCE.md`) — this skill edits nothing
When to use
design-featurefinished a Product half and the roadmap row readsdefined:/review-spec <NN-slug>— this is the mandatory hop before/plan-feature.- After a
design-featurerepair batch produced a newartifactRevisionId. plan-featurerefuses to plan without a current PASS from this skill; it redirects here rather than proceeding.- Not for engineering plans (
review-plan), not for source diffs (review-change), not for merge gating (audit-pr).
What is under review
Only the Product half. The Engineering half must be empty or absent — a
partially filled Engineering half is not a reason to skip this review, and this
skill never reviews it. Fix units have no Product half and never enter this skill
(plan-fix routes to review-plan).
Step 0 — Discover the project (always first)
What ships with it
2 files 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 ac66c147246f
- yesterday First seen · 146 lines · 77 tokens per session scan A 7798b51447cf
review-spec is a skill published in the GitHub repository gtrabanco/agentic-workflow (20 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 1,858 once invoked, about $0.0004 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-09-04.
Other skills, from other repositories
think-like-me
Personal engineering rules and reasoning patterns the user has curated over time. Consult BEFORE writing, modifying, debugging, or designing any technical feature — rules often cover domain-specific gotchas (e.g., mobile audio timers need background mode) that generic answers miss. Also triggers on /learn-this, "learn…
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…