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/commitgit 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.00010 | $0.00832 |
| Opus 5 | $0.00005 | $0.00416 |
| Sonnet 5 | $0.00002 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
Grade A, and why
commit 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Command
Commit staged changes with auto-generated Conventional Commits messages. Works in single repos and superprojects with submodules.
Arguments
Parse the following from $ARGUMENTS:
--specor-s- Optional: spec name to include in commit message--issueor-i- Optional: issue ID to include in commit message (e.g.,#123,PROJ-456)--dry-run- Optional: show planned commits without executing--no-confirm- Optional: show proposal and ask for confirmation before committing (default: auto-confirm)--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. - spec: value after
--specor-s - issue: value after
--issueor-i - dry-run: boolean, true if
--dry-runpresent - no-confirm: boolean, true if
--no-confirmpresent
Help Output
If --help or -h is present, display this and stop:
Usage: /git-workflow:commit [options]
Commit staged changes with auto-generated Conventional Commits message.
Works in single repos and superprojects with submodules.
Options:
-s, --spec <name> Spec name to mention in commit message
-i, --issue <id> Issue ID to reference in commit message (e.g., #123)
--dry-run Show planned commits without executing
--no-confirm Show proposal and ask for confirmation (default: auto-confirm)
-h, --help Show this help message
Examples:
/git-workflow:commit Commit staged changes
/git-workflow:commit -s auth-flow With spec reference
/git-workflow:commit -i "PROJ-123" With issue reference
/git-workflow:commit -s auth-flow -i "#123" With both references
/git-workflow:commit --dry-run Preview without committing
Step 2: Detect Mode
Determine if this is a single repo or superproject:
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 · 105 lines · 10 tokens per session scan A 7074a8d057e5
commit is a command published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 7d ago), licensed MIT. It adds 10 tokens to every session and 832 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.