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/marciopuga/cog/commitgit clone --depth 1 https://github.com/marciopuga/cogWhat 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.00038 | $0.00754 |
| Opus 5 | $0.00019 | $0.00377 |
| Sonnet 5 | $0.00008 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00075 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this skill when the user wants to commit changes to git. Trigger if the user says "commit", "save changes", "commit this", or asks to create a git commit. Examples: "commit", "commit and push", "save my changes".
Process
-
Assess the working tree — Run
git status(never use-uall) andgit diff --stagedandgit diffto understand what changed. -
Guard rails — Before staging:
- Never commit files that contain secrets (
.env, credentials, tokens, keys). Warn if any are present. - Never commit build artifacts (
dist/,*.tsbuildinfo). - Never commit
node_modules/. - If there are no changes to commit, say so and stop.
- Never commit files that contain secrets (
-
Stage selectively — Stage files by name. Prefer
git add <file>...overgit add -Aorgit add .to avoid accidentally including sensitive or unrelated files. Group related changes — if unrelated changes exist, ask whether to commit everything together or separately. -
Write the commit message — Use Conventional Commits format:
feat:new featurefix:bug fixrefactor:code restructuring without behavior changechore:maintenance, dependencies, configdocs:documentation onlystyle:formatting, whitespacetest:adding or updating tests- Scope is optional:
feat(whatsapp): add voice note transcription - Subject line: imperative mood, lowercase, no period, under 72 chars
- Body (if needed): blank line after subject, wrap at 72 chars, explain why not what
- If you are an AI agent, end with a co-author trailer identifying yourself, e.g.
Co-Authored-By: Claude <[email protected]>— use your actual model/agent identity, don't hardcode someone else's
-
Commit — Use a HEREDOC for the message to preserve formatting:
git commit -m "$(cat <<'EOF' type(scope): subject line Optional body explaining why. Co-Authored-By: <your agent identity> <[email protected]> EOF )" -
Verify — Run
git statusafter committing to confirm success. Show the resultinggit log --oneline -1.
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.
- 2d ago First seen · 66 lines · 38 tokens per session scan A 691e31e0a398
commit is a command published in the GitHub repository marciopuga/cog (376 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 754 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-30.
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.