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/lwalden/aiagentminder/briefnpx skills add lwalden/AIAgentMinder --skill briefgit clone --depth 1 https://github.com/lwalden/AIAgentMinderWrote 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/lwalden/aiagentminder/brief)<a href="https://agentmods.dev/skills/lwalden/aiagentminder/brief"><img src="https://agentmods.dev/badge/skills/lwalden/aiagentminder/brief.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.00005 | $0.02650 |
| Opus 5 | $0.00003 | $0.01325 |
| Sonnet 5 | $0.00001 | $0.00530 |
| Haiku 4.5 | $0.00001 | $0.00265 |
Grade A, and why
brief 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 5d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aiagentminder:brief - Product Brief & Roadmap Creation
Create or update docs/strategy-roadmap.md — the project's north star, the "why" behind every development decision.
Before Starting
Read CLAUDE.md to understand the project identity (name, type, stack).
If Project Identity is still placeholder brackets, run /aiagentminder:setup first.
Note: Claude Code has a built-in
/plancommand that toggles Plan Mode (read-only exploration). This command (/aiagentminder:brief) is different — it produces a product brief and strategy roadmap.
Step 0: Assess Starting Point
Ask the user where they are:
A) Rough concept -- "I have a vague idea but need help figuring everything out" B) Clear idea, no details -- "I know what I want but haven't worked out specifics" C) Partial plan or spec -- "I have some docs/notes -- help me fill in gaps" D) Detailed plan or spec -- "I have a writeup -- translate it into a roadmap" E) Existing project -- "The project already has code -- I'm adding AIAgentMinder for governance"
| Starting Point | Approach |
|---|---|
| A) Rough concept | Full interview (all rounds) plus exploratory questions |
| B) Clear idea | Full interview as written below |
| C) Partial plan | Read shared docs, ask only about gaps |
| D) Detailed plan | Generate roadmap directly, clarify ambiguities only |
| E) Existing project | Codebase audit + current-state interview; skip product brief, generate filled state files |
Starting Point E: Existing Project
Skip the product planning interview. The goal is to capture current state, not design a product.
Step E1: Audit the Codebase
Read key files to understand what exists:
CLAUDE.md(if present) -- existing project identity or instructionspackage.json,pyproject.toml,go.mod,Cargo.toml, or equivalent -- stack and dependenciesREADME.md-- project description- Directory structure -- infer architecture
Summarize what you found: language, framework, rough architecture, apparent project stage.
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.
- 5d ago First seen · 207 lines · 5 tokens per session scan A cbadfd11ca93
brief is a skill published in the GitHub repository lwalden/AIAgentMinder (4 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 2,650 once invoked, about $0.0000 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
sdd-serve
Serve the SDD Builder's AI request queue: claim requests with sddnextrequest, draft the proposal, answer with sddrespondrequest. Never writes spec files — the user accepts each proposal in the builder. Use when the user asks to attend, serve or listen to the SDD board queue. / Atiende la cola de peticiones del SDD…
sdd-workflow
Guide a project with Spec-Driven Development (SDD) discipline - idea, approved spec, consistent plan, tasks, a gate that verifies approval and consent, implementation, validation, and logbook. Bilingual EN/ES. Use when the user wants to start, spec, plan, implement, or validate work with SDD, or mentions specs, plans…
metrics-instrumentation
Specification for instrumenting an opik-backend workflow with operational OpenTelemetry metrics — per-stage throughput/latency/error counters and native histograms, dimensioned per-customer (workspace). Use when a pipeline (scoring, ingestion, experiments, jobs) needs per-stage visibility. Covers metric emission only…
notifications
Send notifications through the unified notification router.
release
Cut a sim-use release end-to-end. Use when the user runs /release or asks to "ship a release", "publish a version", "cut a release", or "release to homebrew". Drives scripts/local-release.sh; never reimplement its build/sign/tarball logic.
vellum-skills-catalog
Discover bundled skills and search/install community skills from the skills.sh registry.