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 VPDPersonal/Aspid.FastTools --skill asp-commitgit clone --depth 1 https://github.com/VPDPersonal/Aspid.FastToolsWrote 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/vpdpersonal/aspid.fasttools/asp-commit)<a href="https://agentmods.dev/skills/vpdpersonal/aspid.fasttools/asp-commit"><img src="https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/asp-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/vpdpersonal/aspid.fasttools/asp-commit"><img src="https://agentmods.dev/badge/skills/vpdpersonal/aspid.fasttools/asp-commit.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.00029 | $0.01308 |
| Opus 5.5 | $0.00012 | $0.00523 |
| Sonnet 5.5 | $0.00006 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
asp-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 today.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sh ${CLAUDE_SKILL_DIR}/scripts/ctx.sh
No output above? Your agent does not run this block: run sh scripts/ctx.sh from the folder of this file. There, ${CLAUDE_SKILL_DIR} is that folder.
Hint lines
| Line | Action |
|---|---|
GONE |
The branch was merged and deleted on origin. Ask with AskUserQuestion first. |
CLEAN |
Nothing to commit. Go to Push only. |
AHEAD, NO_UPSTREAM |
Used only in Push only. |
BRANCH new |
Branch step: git switch -c <name>. |
BRANCH rename |
Branch step: git branch -m <name>. The app made this worktree branch, and origin does not have it yet. |
SKIP_ADD <path> |
The path is already gone from the index. Keep it in git commit -- <paths>, but not in git add. |
Before a branch step, load the asp-branch skill to get <name>.
Pick the files
- Take the files you changed in this session and the files the user named.
- Add the Unity
.metafiles of these files and of their folders. - Take paths only from the status lines. A file inside
?? <dir>/counts. - A changed file is not in the status? In another repo, see Special cases. Otherwise it is ignored: skip it.
- Changes that are not yours and that the user did not name? Ask with
AskUserQuestionwhether to add them. - Run
git diff -- <file>only for a file you did not change.
Commit and push: one Bash call, no subagents
- Write the subject:
type(scope): imperative summary, 72 chars max, no period. - Add a body of 2–4 bullets only if there are more than 5 files or the reason is not clear.
- Run the chain. At
TOO LONG, rewrite the subject to 65 chars or fewer. Then run the chain again. - Report the commits in a table with the columns: subject, short SHA, push. List the skipped files below the table.
In the push column, write the branch name, for example
feat/login. Do not use the SHA range orHEAD. Writefailedif the push failed.
Run no other git commands, except git diff in Pick the files and in Special cases.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 94 lines · 29 tokens per session scan A 885557a9adbc
asp-commit is a skill published in the GitHub repository VPDPersonal/Aspid.FastTools (24 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,308 once invoked, about $0.0001 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-10-17.
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 8. 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.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.