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 agents/hackersandwizards/artificer/sdlc-9-commitgit clone --depth 1 https://github.com/hackersandwizards/artificerWrote 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/agents/hackersandwizards/artificer/sdlc-9-commit)<a href="https://agentmods.dev/agents/hackersandwizards/artificer/sdlc-9-commit"><img src="https://agentmods.dev/badge/agents/hackersandwizards/artificer/sdlc-9-commit.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00018 | $0.00254 |
| Opus 5 | $0.00009 | $0.00127 |
| Sonnet 5 | $0.00004 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
sdlc-9-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 4d ago.
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.
What it actually says
Commit the changes this workflow produced on the current branch.
- Read the previous stage's summary, then run
git statusandgit diffto see exactly what changed. - Stage the feature and test files and commit them in a single commit. Do not push, do not amend, do not create a branch.
- Write a concise commit message matching the repo's existing style (check
git log), summarizing the feature, its tests, and the acceptance outcome. - Leave no staged changes behind.
- Output the commit SHA and subject as the handoff to the report stage.
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.
- 4d ago First seen · 21 lines · 18 tokens per session scan A 7b0e7545775f
sdlc-9-commit is an agent published in the GitHub repository hackersandwizards/artificer (16 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 254 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-30.
Other agents, from other repositories
06_GIT_DELIVERY_AGENT
When delivery is assigned, stage explicit scoped paths only, commit with the ticket ID prefix, push to the configured upstream, and prove equality.
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
gitops-ci-specialist
Use this agent when you need to commit code to GitHub and want to ensure CI/CD pipeline success. Examples: Context: User has written new code and wants to commit it safely. user: 'I've added a new authentication module. Can you help me commit this properly?' assistant: 'I'll use the gitops-ci-specialist agent to…
claude-code-hook-agent
Plays agent-specific sounds for the 6 hooks that actually fire in agent sessions.
quality-gates
Runs the repo's quality gates (lint, format, typecheck, dead-code, scoped tests) and returns a concise pass/fail report. Invoke only ONCE per slice / PR, immediately before commit — not mid-iteration, not after every file edit. Before delegating, the caller should run the project's auto-formatter on touched files…
lynx-specialist
Expert consultant for Lynx framework development, modern desktop applications with web technologies, and native performance optimization. Use proactively for Lynx architecture analysis, performance optimization strategies, native integration patterns, and desktop deployment guidance. Provides consultation and…