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/resultgit 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.00019 | $0.01493 |
| Opus 5 | $0.00010 | $0.00746 |
| Sonnet 5 | $0.00004 | $0.00299 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
result 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Result Review Command
Review implementation against a spec by analyzing git diffs and cross-referencing with spec requirements.
Arguments
Parse the following from $ARGUMENTS:
[path...]— One or more spec file or folder paths (positional args)--baseor-b— Branch to compare against (e.g.,develop,main). Uses<base>...HEAD--fix— Enable iterative review → fix loop with parallel multi-angle review--fix-all— Auto-fix all severities including critical/high (implies--fix)--no-parallel— Disable parallel multi-angle review (requires--fix)--parallel <angles>— Custom review angles, comma-separated (requires--fix)-n <N>or--max-iterations <N>— Maximum iteration rounds, default 3 (requires--fix)--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. - paths: collect all positional arguments (not flags or flag values)
- base: value after
--baseor-b(if provided) - fix: true if
--fixis present, or if--fix-allis present - fix_all: true if
--fix-allis present - no_parallel: true if
--no-parallelis present - angles: value after
--parallel(comma-separated string), or "default" if not provided - max_iterations: integer value after
-nor--max-iterations, default 3
Help Output
If --help or -h is present, display this and stop:
Usage: /reviewer:result [path...] [options]
Review implementation against a spec using git diffs.
Positional arguments:
path... Spec files or folders to review against
Options:
-b, --base <branch> Compare <branch>...HEAD (default: auto-detect)
-h, --help Show this help message
Diff strategy:
With --base: git diff <base>...HEAD
Without --base: Auto-detect base branch, or use git diff + git diff --cached
Fix mode options:
--fix Enable iterative review → fix loop
--fix-all Auto-fix all severities (implies --fix)
--no-parallel Use single-agent review instead of multi-angle parallel
--parallel <angles> Custom review angles (comma-separated)
Default angles: coverage, robustness, correctness
-n, --max-iterations <N> Maximum rounds (default: 3)
Examples:
/reviewer:result docs/plans/auth-flow/
/reviewer:result spec.md tasks.md --base develop
/reviewer:result docs/plan/ -b main
/reviewer:result # asks which spec to review
# Iterative review + auto-fix (default: 3 rounds, parallel multi-angle)
/reviewer:result docs/plan/ --fix
# With base branch, single-agent, max 5 rounds
/reviewer:result docs/plan/ --fix --base main --no-parallel -n 5
# Fix all severities (implies --fix)
/reviewer:result docs/plan/ --fix-all
# Custom angles, fix all severities
/reviewer:result docs/plan/ --fix-all --parallel "security,coverage"
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 · 169 lines · 19 tokens per session scan A c0b53be45f6c
result is a command published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 19 tokens to every session and 1,493 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.