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 kimtth/agent-skill-100-lines-or-less --skill finishing-a-development-branchgit clone --depth 1 https://github.com/kimtth/agent-skill-100-lines-or-lessWrote 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/kimtth/agent-skill-100-lines-or-less/finishing-a-development-branch)<a href="https://agentmods.dev/skills/kimtth/agent-skill-100-lines-or-less/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/kimtth/agent-skill-100-lines-or-less/finishing-a-development-branch/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/kimtth/agent-skill-100-lines-or-less/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/kimtth/agent-skill-100-lines-or-less/finishing-a-development-branch.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.00033 | $0.00235 |
| Opus 5 | $0.00016 | $0.00118 |
| Sonnet 5 | $0.00007 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
finishing-a-development-branch 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 11d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 11d ago First seen · 32 lines · 33 tokens per session scan A 1aa4de3be903
finishing-a-development-branch is a skill published in the GitHub repository kimtth/agent-skill-100-lines-or-less (2 stars, last pushed 2mo ago), with no licence file. It adds 33 tokens to every session and 235 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-31.
Other skills, from other repositories
spec-kitty-git-workflow
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…
spk-admin-git-workflow
Operate Spec Kitty git workflows, worktrees, safe commits, merge preflights, stale state checks, and recovery.
spk-gate-merge
Merge an accepted Spec Kitty mission safely, preserving git invariants, mission state, and post-merge follow-through.
056-design-avoid-breaking-changes
Use when you need to review a plan, OpenSpec change, specification, or implementation proposal for breaking-change risk across commands, skills, generated outputs, XML sources, README/docs, tests, CI, APIs, schemas, configuration, data, migration, and release guidance. This should trigger for requests such as Review…
pr-comment-review
Audit and remediate an open GitHub PR's review feedback: verify Copilot and Codex actually reviewed, drive every unresolved thread to a fix-or-justify reply, correct PR title/description drift against the real diff, and run a one-time self-review pass. Trigger on "have all PR comments been addressed", "did copilot and…
changelog-rewriter
Rewrites changelog entries with cheeky, narrative flair following project conventions. Use this when asked to rewrite or update CHANGELOG.md entries.