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 tamnguyendinh/Anvien --skill plannergit clone --depth 1 https://github.com/tamnguyendinh/AnvienWrote 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/tamnguyendinh/anvien/planner)<a href="https://agentmods.dev/skills/tamnguyendinh/anvien/planner"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/planner/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/tamnguyendinh/anvien/planner"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.02576 |
| Opus 5 | $0.00010 | $0.01288 |
| Sonnet 5 | $0.00004 | $0.00515 |
| Haiku 4.5 | $0.00002 | $0.00258 |
Grade A, and why
planner 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 yesterday.
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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner With Anvien
Use this skill when work involves creating, reviewing, or updating a plan under docs/plans.
This skill is a workflow gate for plan/evidence/benchmark/actual-status authoring. It is not a command router. When a concrete Anvien command is needed for implementation evidence, choose it directly from the generated Command Selection Guide.
Standard Plan Set
A standard plan is a five-file set with the same date and slug:
docs/plans/YYYY-MM-DD-<slug>/
YYYY-MM-DD-<slug>-plan.md
YYYY-MM-DD-<slug>-rules.md
YYYY-MM-DD-<slug>-evidence.md
YYYY-MM-DD-<slug>-benchmark.md
YYYY-MM-DD-<slug>-actual-status.md
Rules:
- Put all five standard files in
docs/plans/YYYY-MM-DD-<slug>/. - Use ISO date format:
YYYY-MM-DD. - Use lowercase ASCII kebab-case for the slug.
- Keep the same slug in all five standard files; only the suffix changes.
- When writing a plan, you must follow the template exactly 100% (planner\templates\actual-status.template.md, planner\templates\benchmark.template.md, planner\templates\evidence.template.md, planner\templates\plan.template.md, planner\templates\rules.template.md).
- Use the matching H1:
Plan,Plan Rules,Evidence Ledger,Benchmark Ledger, orActual Status. - Auxiliary files such as
*-remaining-files.mdcan exist, but they are not part of the standard five-file set.
Template Files
Use the bundled templates before writing a new standard plan set:
templates/plan.template.mdtemplates/evidence.template.mdtemplates/benchmark.template.mdtemplates/actual-status.template.md
Rules:
- Start from these templates instead of inferring structure from older nearby plans.
- Read nearby plans only for local naming, scope, or evidence conventions that are clearly still active.
- Replace template placeholders with the concrete date, slug, title, companion file paths, and task scope.
- Keep template sections that protect discipline unless a user explicitly asks for a smaller review-only artifact.
What ships with it
4 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.
- yesterday Changed · +19 lines 67523bae9ab5
- 6d ago First seen · 209 lines · 20 tokens per session scan A d523220f7182
planner is a skill published in the GitHub repository tamnguyendinh/Anvien (9 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 2,576 once invoked, about $0.0001 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-03.
Other skills, from other repositories
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
product-manager-toolkit
Use when the user needs product management workflows such as RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, go-to-market strategy, feature prioritization, research synthesis, or requirements documentation.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
mention-conventions
Display @-mention naming conventions and placement rules.
mention-lint
Lint @-mentions for style consistency and correctness.