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/modiqo/skillspec/sourcenpx skills add modiqo/skillspec --skill sourcegit clone --depth 1 https://github.com/modiqo/skillspecWhat 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 | $0.00116 | $0.02842 |
| Opus 5 | $0.00058 | $0.01421 |
| Sonnet 5 | $0.00023 | $0.00568 |
| Haiku 4.5 | $0.00012 | $0.00284 |
Grade A, and why
code-review 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Orchestrate a multi-agent code review pipeline: research the changes, optionally investigate external alternatives, dispatch parallel domain-specific reviewers, and synthesize everything into a structured report.
Input Collection
Prompt the user to select an input mode. Present these options clearly:
What would you like me to review?
- Current PR — review the open PR on this branch (description + diff)
- Diff to main — review all uncommitted and committed changes vs main
- Specific paths — review specific files, crates, or directories
Pick a number, or describe what you'd like reviewed.
Collecting the diff
Mode 1 — Current PR:
gh pr view --json title,body,number,baseRefName
gh pr diff
If no open PR exists, tell the user and suggest mode 2 instead.
Mode 2 — Diff to main:
git diff main...HEAD
Also include git log main..HEAD --oneline for commit context.
Mode 3 — Specific paths: Ask the user for paths. Read the specified files directly. No diff — review the code as-is.
Store the collected input (diff text, PR description, file contents) for use in subsequent phases.
Handling large diffs
If the diff exceeds ~2000 lines, save it to a temporary file (/tmp/code-review-diff.patch) and have agents read it via the Read tool rather than inlining it in their prompts. This prevents context overflow. Reference the file path in agent prompts instead of pasting the diff.
Phase 1: Research & Domain Mapping
Spawn an Agent (subagent_type: general-purpose) and include the full text of the research-codebase skill instructions in its prompt (read .claude/skills/research-codebase/SKILL.md first). Direct the agent to research the changes with this focus:
- Map all changed files to their logical domains and crate boundaries
- Identify which changes are Rust code vs non-Rust (CI, docs, config, TypeScript SDK, nix, etc.)
- Understand the architectural context around each change — what traits, types, and modules are involved
- Group changes into at most 4 logical domain groups, merging smaller related changes together
- Flag any changes that warrant external web research:
- New dependencies or crate additions
- Unfamiliar architectural patterns
- Potentially deprecated API usage
- Cases where alternative approaches might exist
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.
- 2d ago First seen · 233 lines · 116 tokens per session scan A 4f7600536360
code-review is a skill published in the GitHub repository modiqo/skillspec (737 stars, last pushed 24d ago), licensed Apache-2.0. It adds 116 tokens to every session and 2,842 once invoked, about $0.0006 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-30.
Other skills, from other repositories
writing-e2e-flows
Use when a feature or fix in future-agi needs an end-to-end Playwright flow under e2e/ — a new flow for user-visible behaviour, an update to a flow whose pinned endpoint, route, table or selector changed, or when a review flagged missing E2E coverage. Also use to check whether an existing flow already pins an…
reviewing-prs
Use when asked to review a pull request, branch, or diff — before approving, as a self-review before opening a PR, to judge whether a PR is ready — 'is PR 123 mergeable?', 'anything blocking here?' — or to answer 'does this change need an E2E flow'. Applies the FutureAGI coding standards and, in repos with an e2e/…
ashfox
Create, edit, review, animate, and export game-ready low-poly assets in the ashfox web workbench through an AI agent. Use for low-poly modeling, deterministic textures and UVs, rigs, idle or motion animation, GLB, Bedrock, or GeckoLib exports, and Blockbench-free asset production.
ui-2026-cinematic
Cinematic 3D / scroll-driven / motion design skill for landing pages in 2026. Use when building marketing pages, SaaS sites, or product showcases that need scroll storytelling, 3D elements, micro-interactions, kinetic typography, or glassmorphism. Encodes modern best practices from Figma, Anthropic, Apple, Vercel.…
template-skill
A minimal template for creating a new FDE Consultant Skill (Apache-2.0). Use as starting point for any new skill.
production-autopsy
Start here. Audits a deployed ML or LLM or agent system that scores well on evaluation but fails, regresses, or behaves unexpectedly in production. Runs a reproducible root-cause "autopsy": frames the eval-to-deployment gap, reproduces the production failure, quantifies it by slice, tests confidence calibration under…