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 skills add congchuanling-dot/Cohort --skill commitgit clone --depth 1 https://github.com/congchuanling-dot/CohortWrote 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/congchuanling-dot/cohort/commit)<a href="https://agentmods.dev/skills/congchuanling-dot/cohort/commit"><img src="https://agentmods.dev/badge/skills/congchuanling-dot/cohort/commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/congchuanling-dot/cohort/commit"><img src="https://agentmods.dev/badge/skills/congchuanling-dot/cohort/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.01019 |
| Opus 5.5 | $0.00024 | $0.00408 |
| Sonnet 5.5 | $0.00012 | $0.00204 |
| Haiku 4.5 | $0.00006 | $0.00102 |
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 1mo 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineer enforcing atomic, FAANG-level commit discipline.
Rules
- Atomic — one logical change per commit, never mix features with docs or refactors
- Never use
git add .orgit add -A— always stage specific files - Conventional Commits format:
type(scope): short imperative description - Body required when there are non-obvious decisions — explain the why, not the what
- No body needed when the subject line is self-explanatory
- Subject line: max 72 characters, imperative mood ("add" not "added")
- Body: prose only — no bullets, no numbered lists, no dashes
- Body: max 2 sentences — if you need more, the commit is too big
- Body: wrap at 72 characters per line
- No AI attribution — no Co-Authored-By, no Claude mentions
Commit types
| Type | When |
|---|---|
feat |
New feature or test slice |
fix |
Bug fix |
refactor |
Code change with no behaviour change |
test |
Adding or updating tests only |
docs |
README, comments, ADRs |
chore |
Config, dependencies, CI |
perf |
Performance improvement |
Process
Step 1 — Discover changes
Run git status and git diff to understand what changed.
List the changed files and ask the user which ones to include if $ARGUMENTS is empty.
If $ARGUMENTS specifies files, stage only those.
If there are no changes (clean working tree), tell the user and stop.
Step 2 — Analyse the changes
Read the staged files to understand what changed, why, and what type applies.
Split test — ask these three questions:
- Can I revert one change without losing the other? (e.g. config vs applying config)
- Would the diff make sense to a reviewer as a single unit?
- Does the subject line need "and"? If yes, it's two commits.
If any answer points to a split, recommend it with the specific grouping (e.g. "config files in commit 1, formatted code in commit 2").
Step 3 — Draft the commit message
Write subject line + body if needed.
Body is required when:
- A non-obvious technical decision was made (e.g. returning Locator instead of string[])
- A pattern was chosen over an alternative (e.g. guard assertion before removal)
- A known pitfall was avoided (e.g. race condition, unfalsifiable test)
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.
- 1mo ago First seen · 133 lines · 59 tokens per session scan A 2c96e34fa8bb
commit is a skill published in the GitHub repository congchuanling-dot/Cohort (183 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 1,019 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
github-code-review
Review PRs: diffs, inline comments via gh or REST.
github-auth
GitHub auth setup: HTTPS tokens, SSH keys, gh CLI.
github-repo-management
Clone, create, fork repos; manage remotes, releases.
akigitcommit
Analyze the working tree and commit changes in clean logical groups. Triages a long half-finished tree first (finished vs mid-edit vs abandoned vs accidental) before grouping. Auto-detects CHANGELOG to switch between domain-grouped mode (3–5 commits by object/feature) and type-grouped mode (feat/fix/refactor). Stages…
ship-change
Ship an OpenSpec change after openspec-apply completes. When only QA/manual tasks remain, marks them done (tested later), archives + syncs specs, commits, pushes, opens a PR against develop, watches CI, waits for CodeRabbit, auto-applies safe fixes and re-pushes, loops until CI green + no actionable review threads…