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 skills/atman-33/workhub/commit-changesnpx skills add atman-33/workhub --skill commit-changesgit clone --depth 1 https://github.com/atman-33/workhubWhat 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.00044 | $0.00369 |
| Opus 5 | $0.00022 | $0.00185 |
| Sonnet 5 | $0.00009 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
commit-changes 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.
What it actually says
Commit the current changes with a Conventional Commits message.
Steps
-
Assess the working tree. Run
git status --shortandgit diff(orgit diff --stagedif changes are already staged) to see what changed and why.- Completion criterion: the changed files and their purpose are known.
-
Stage changes. If nothing is staged, run
git add ..- Completion criterion: at least one change is staged.
-
Draft the message. Pick a Conventional Commits prefix based on the diff:
feat— new featurefix— bug fixdocs— documentation onlystyle— formatting, missing semicolons, etc.refactor— code change that neither fixes a bug nor adds a featuretest— adding or correcting testschore— build process or auxiliary tool/library changes Then write a short imperative description in<type>: <description>format. Use English unless the user requested another language.- Completion criterion: the message follows the format and matches the change.
-
Commit. Run
git commit -m "<message>".- Completion criterion: the commit succeeds and its hash is shown.
Failure modes
- No changes to commit: stop and report.
gitnot in a repository: stop and report.- Multiple unrelated changes: consider splitting into multiple commits and ask the user.
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 · 34 lines · 44 tokens per session scan A a804bdebd0cb
commit-changes is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 369 once invoked, about $0.0002 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 skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
memory
Use this skill when Pioneer should proactively use durable memory or recalled context: decide whether memory can improve a turn, answer from remembered user/project facts, request memory tools, search/list/get stored memories, save durable preferences or project decisions, forget memories, audit or clean up memory, or…
subagents
Use this skill when Pioneer should delegate current-turn work to attached task-backed subagents, coordinate parallel child agents, wait for child results, review/revise/accept/cancel/detach attached work, or synthesize accepted child results into the parent answer.
writing-staffing
Dispatch reference for composing writing teams. Teaches which extra skills to attach via --skills, which resources to reference in spawn prompts, and when to fan out versus run parallel lanes. Load when staffing a workflow.
trellis-meta
Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, workflows, the channel runtime (trellis channel), bundled runtime agents under .trellis/agents/, selectable workflow templates, registry-backed…
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…