Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add digital-stoic-org/agent-skills/plugin install dstoicWrote 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/skills/digital-stoic-org/agent-skills/commit-repo)<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/commit-repo"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/commit-repo.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.1 | $0.00041 | $0.01281 |
| Opus 5 | $0.00020 | $0.00641 |
| Sonnet 5 | $0.00008 | $0.00256 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade B, and why
commit-repo scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Add auto-approve rules for read-only git commands on each repo path. Example for `~/.claude/settings.json`: How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Repo
Streamlined commit flow for praxis-managed repos. One human gate only.
Repo Resolution
Resolve <repo-alias> to a git-managed path:
- If alias is the project root name (e.g.,
praxis): use CWD (the project root itself) - Otherwise: look up alias in CLAUDE.md → Alias Paths section, extract the
datapath
Example CLAUDE.md format:
## Alias Paths
- **nano-vc**: control `$PRAXIS_DIR/repos/nano-vc` | data `/home/mat/dev/nano-vc`
- **agent-skills**: control `$PRAXIS_DIR/repos/agent-skills` | data `/home/mat/dev/agent-skills`
The data value = the git repo path to commit in.
If alias not found, list available aliases from CLAUDE.md and exit.
Arguments
$ARGUMENTSfirst word = repo alias (required)--allflag: stage all modified files before committing (runsgit add -A)--yesflag: skip human confirmation gate — auto-approve the commit proposal- Without
--all: only commits what's already staged
Flow
CRITICAL: Each git command MUST be a separate Bash call. NEVER chain with &&, ||, or ;. This enables auto-approval via permission rules.
Phase 1: Recon (auto-approved, no human gate)
Run these as separate sequential Bash calls:
git -C <data-path> statusgit -C <data-path> diff --staged(if no--allflag) ORgit -C <data-path> diff(if--allflag, to show what will be staged)git -C <data-path> log --oneline -5
Phase 2: Analyze + Propose
From the recon output:
- List files that will be committed (staged files, or all modified if
--all) - Determine conventional commit
type(scope): descriptionper CLAUDE.md rules - Draft commit body:
What:bullets +Why:line
Phase 3: Propose + Confirm + Execute
- Output the proposal as text:
---
📦 Commit proposal for <alias> (<branch>)
Staged files:
- file1
- file2
Commit message:
type(scope): description
What:
- change 1
- change 2
Why: reason
- If
--yesflag is set: skip confirmation, proceed directly to step 3. Otherwise — ⚠️ MANDATORY HUMAN GATE — use AskUserQuestion:- Question: "Proceed with commit? (y/n/edit)"
- If answer is empty/blank (known bug outside Plan Mode): fall back to inline text — output "Reply y to commit, n to abort, or edit to modify" and WAIT for user text reply
- If "n" or denied: abort, report "❌ Commit aborted"
- If "edit": ask what to change, revise, re-propose
- If "y" or approved: proceed to step 3
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.
- 7d ago First seen · 149 lines · 41 tokens per session scan B a3499be70952
commit-repo is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 1,281 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…