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 lacvietanh/akidevrule --skill akigitcommitgit clone --depth 1 https://github.com/lacvietanh/akidevruleWrote 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/lacvietanh/akidevrule/akigitcommit)<a href="https://agentmods.dev/skills/lacvietanh/akidevrule/akigitcommit"><img src="https://agentmods.dev/badge/skills/lacvietanh/akidevrule/akigitcommit/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/lacvietanh/akidevrule/akigitcommit"><img src="https://agentmods.dev/badge/skills/lacvietanh/akidevrule/akigitcommit.svg" alt="Reviewed on agentmods" width="80" 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.00100 | $0.01518 |
| Opus 5.5 | $0.00040 | $0.00607 |
| Sonnet 5.5 | $0.00020 | $0.00304 |
| Haiku 4.5 | $0.00010 | $0.00152 |
Grade A, and why
akigitcommit 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
akigitcommit — scientific grouped commits
Invoke with /akigitcommit. Goal: turn a messy working tree into a small set of clean, logically grouped commits — without ever losing staging from one group to the next.
Step 0 — triage a half-finished tree
Run this only when the tree is not uniformly finished: many changed files, a mix of committed and uncommitted work, edits visibly stopped mid-way, or the user asks to audit the tree before committing. A clean, coherent set of changes skips straight to mode detection.
Triage is an audit, so RULE-agent-behavior.md B5 applies in full — most importantly: never run git add, stash, checkout, restore, clean, or reset during triage. This is exactly the state in which uncommitted work is most valuable and least recoverable, and "tidying up" is the shape the loss usually takes.
Classify every chunk into one of four:
| Class | Signal | Disposition |
|---|---|---|
| Finished | a closed problem, coherent on its own | proceeds to grouping below |
| Mid-edit | intentional, the author is still on it | hold — do not commit inside someone's unfinished thought |
| Abandoned | an experiment that went nowhere | ask before anything; never discard on your own read |
| Accidental | debug prints, scratch files, temp output in the project tree (RULE-agent-behavior.md C5) |
flag with the path; do not auto-delete |
Mid-edit and abandoned cannot be told apart by reading the tree — only the author knows which one a half-written function is. Present both as unclassified and ask; a guess here silently commits dead code or buries live work.
Output a short list (class, paths, one line each) and let the user confirm before grouping. If the leftovers will not be resolved in this session, they belong in a docs/plan/ note, not docs/research/ — a snapshot of today's tree is false tomorrow (RULE-docs.md C1).
Mode detection (run after triage)
Before grouping, check: does the repo have a CHANGELOG.md?
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 Changed 350a2455329b
- 1mo ago First seen · 86 lines · 100 tokens per session scan A b26697710d32
akigitcommit is a skill published in the GitHub repository lacvietanh/akidevrule (10 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 1,518 once invoked, about $0.0004 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-31.
Other skills, from other repositories
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…
starfleet-sessions
Ship session and workspace management — spawning ships, session attach/stop, git worktrees, web console, deployment. Load when launching/administering ships or managing the fleet web console.
starfleet-github
GitHub PR/CI/backport interaction via starfleetctl (read-only + mutating commands, PR claims, backports). Load when checking PR status/CI, claiming a PR branch, submitting or repairing a PR, or backporting.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…