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 commands/shdennlin/agent-plugins/initgit clone --depth 1 https://github.com/shdennlin/agent-pluginsWhat 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.00016 | $0.01551 |
| Opus 5 | $0.00008 | $0.00776 |
| Sonnet 5 | $0.00003 | $0.00310 |
| Haiku 4.5 | $0.00002 | $0.00155 |
Grade A, and why
init 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init Command
Inject reviewer rules into your project's openspec/config.yaml so that specs generated
by OpenSpec tooling already satisfy the reviewer's criteria.
Arguments
Parse the following from $ARGUMENTS:
--dry-runor-n— Preview rules that would be added without writing--from-history— Harvest recurring review findings into candidate rules--helpor-h— Show usage information and exit
Instructions
Step 1: Parse Arguments
From $ARGUMENTS, extract:
- help: if
--helpor-his present, show the usage information below and stop. Do NOT delegate to the agent. - dry_run: if
--dry-runor-nis present, set dry_run = true - from_history: if
--from-historyis present, set from_history = true
Help Output
If --help or -h is present, display this and stop:
Usage: /reviewer:init [options]
Inject reviewer rules into openspec/config.yaml so specs pass review on first attempt.
Options:
-n, --dry-run Preview what would be added without writing
--from-history Harvest recurring review findings into candidate rules
-h, --help Show this help message
What it does:
Reads your project's openspec/config.yaml and appends rules for each artifact
(proposal, specs, design, tasks) based on the reviewer's focus areas.
Existing rules are preserved — only new rules are appended (dedup by exact match).
With --from-history, reads the review findings history (openspec/reviews/history.jsonl
or .claude/reviewer/history.jsonl), clusters findings that recur across 2+ changes into
candidate rules, asks you to confirm each, and injects only the confirmed ones.
The same pass flags existing rules for retirement (finding class never seen in history,
or superseded by a new rule) — removals are confirmed separately before applying.
Examples:
/reviewer:init # inject rules into openspec/config.yaml
/reviewer:init --dry-run # preview without writing
/reviewer:init -n # same as --dry-run
/reviewer:init --from-history # cluster review history into new rules
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 First seen · 150 lines · 16 tokens per session scan A ba59af51621e
init is a command published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 7d ago), licensed MIT. It adds 16 tokens to every session and 1,551 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.