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/kintecus/build/review-prepnpx skills add kintecus/build --skill review-prepgit clone --depth 1 https://github.com/kintecus/buildWrote 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/kintecus/build/review-prep)<a href="https://agentmods.dev/skills/kintecus/build/review-prep"><img src="https://agentmods.dev/badge/skills/kintecus/build/review-prep.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 | $0.00083 | $0.01093 |
| Opus 5 | $0.00042 | $0.00547 |
| Sonnet 5 | $0.00017 | $0.00219 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
review-prep 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 4d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Prep
Produce a 2-minute punch list that an operator opens before a project review. The job is not to summarize the docs - it is to derive meaning across them: surface what needs a human decision, what quietly stalled, and what no single doc says on its own.
Which project
If the user named a project, use it. If they ran this from inside a project context, use that. If ambiguous, ask which project (one short question, do not guess).
How to run it - use a fresh-context agent
Dispatch a fresh general-purpose agent to read the artifacts and produce the doc. Do NOT do the reading-and-synthesis yourself in the main conversation - if you have been working on the project this session, your context is polluted by what you already know, and you will miss exactly the cross-artifact findings that make this valuable (the whole point is catching what the operator's own working memory misses). Hand the agent only the project root and these instructions.
The agent reads, in order:
STATUS.md- current state, active threads, open questions, next actionsdocs/INDEX.md- the one-line index of every doc; read this to know what exists before opening anything, then open only the live threads (judge from dates - what is active now)- The most recent / most active
docs/files - not all of them, just the ones the index shows are live decisions/*.md- the decision log
Pass the agent today's date explicitly.
Output format - exactly these five sections
1. Project pulse - one line per active thread (skip dormant ones). Format: thread - RED/AMBER/GREEN - the single most important fact about its current state (source: filename). Judge the color: green = moving, amber = waiting/at-risk, red = blocked or overdue.
2. Decisions waiting on the operator - the 3-7 things that genuinely need the operator's judgment now. Each phrased as a crisp question, with a source. Do NOT pad - if it's already decided, it doesn't belong here. Quality over quantity.
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.
- 4d ago First seen · 56 lines · 83 tokens per session scan A 433564854e72
review-prep is a skill published in the GitHub repository kintecus/build (2 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 1,093 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-08-31.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
finn-spec
Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.