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/checkgit 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.00009 | $0.00746 |
| Opus 5 | $0.00005 | $0.00373 |
| Sonnet 5 | $0.00002 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
check 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mermaid Check Command
Validate and fix Mermaid diagram syntax in Markdown files.
Arguments
[file]- Optional: Specific file to check (e.g.,README.md)--fix- Auto-fix common syntax errors--all- Check all.mdfiles in project (not just git changes)
Default behavior: Only check git changed/staged/untracked .md files.
Instructions
Step 1: Determine Files to Check
Based on arguments ($ARGUMENTS):
| Argument | Action |
|---|---|
| No args | Get git changed .md files |
filename.md |
Check only that file |
--all |
Check all .md files |
Git commands to find changed files:
git diff --name-only --cached --diff-filter=ACMR | grep '\.md$' # staged
git diff --name-only --diff-filter=ACMR | grep '\.md$' # modified
git ls-files --others --exclude-standard | grep '\.md$' # untracked
Step 2: Find Mermaid Blocks
For each file, search for mermaid code blocks:
- Pattern:
```mermaid...``` - Record file path and line number of each block
Step 3: Validate Syntax
Check for common errors:
- Unclosed brackets:
A[Start --> B→ should beA[Start] --> B - Missing graph type: No
graph/flowchart/sequenceDiagramdeclaration - Invalid arrows:
->instead of--> - Unquoted special chars:
A[Hello!]→A["Hello!"]
If mmdc is available, use for deep validation:
echo "diagram content" > /tmp/test.mmd
mmdc -i /tmp/test.mmd -o /tmp/test.svg 2>&1
Step 4: Report Results
Show results in format:
📊 Mermaid Validation Results
❌ Error in file.md:15
graph TD
A[Start --> B[End]
Problem: Unclosed bracket in node A
Fix: A[Start] --> B[End]
Step 5: Fix (if --fix)
If --fix flag present or user requests:
- Propose the fix
- Ask for confirmation (unless obvious fix)
- Use Edit tool to apply
- Re-validate after fixing
Complex Operations
For --fix or --all flags, delegate to the mermaid-validator agent:
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 · 111 lines · 9 tokens per session scan A 8918d9b09139
check is a command published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 746 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 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.