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 kBashar/myagentskills --skill simplagit clone --depth 1 https://github.com/kBashar/myagentskillsWrote 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/kbashar/myagentskills/simpla)<a href="https://agentmods.dev/skills/kbashar/myagentskills/simpla"><img src="https://agentmods.dev/badge/skills/kbashar/myagentskills/simpla/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/kbashar/myagentskills/simpla"><img src="https://agentmods.dev/badge/skills/kbashar/myagentskills/simpla.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.00052 | $0.02854 |
| Opus 5.5 | $0.00021 | $0.01142 |
| Sonnet 5.5 | $0.00010 | $0.00571 |
| Haiku 4.5 | $0.00005 | $0.00285 |
Grade A, and why
simpla 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 yesterday.
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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
simpla
Overview
Cut the lines that a change adds. The order of preference is delete >> simplify >> keep as is. The behaviour stays the same: every test that passed before passes after, or simpla deleted it on purpose under a trivial-test rule.
simpla is not /simplify. /simplify is a quality pass that keeps the tests. simpla is a line-count cut: it deletes first, trivial tests too.
These sit in this skill's base directory (the path shown when the skill loads):
contract.md: the rules that every editor follows, you and each lane. Read it now.scripts/:snapshot.sh,added-lines.shandgone-names.sh. Run them withbashfrom inside the target repository.
Input
| Command | Scope |
|---|---|
/simpla |
The uncommitted changes: modified tracked files against HEAD, plus the untracked files. |
/simpla <base-ref> |
The branch since the merge base with <base-ref>, plus the uncommitted changes. |
The first word is the base ref when git rev-parse --verify --quiet "<word>^{commit}" succeeds. Other text after the command is an instruction from the user. It wins over this skill.
Workflow
Make one todo for each step.
1. Measure and snapshot
Pick a new directory outside the repository: the session scratchpad when there is one, else ${TMPDIR:-/tmp}/simpla-<repo>-<time>. Below, <snap> is that directory.
bash <skill-dir>/scripts/snapshot.sh <snap> [base-ref]
The script saves every file in the scope and counts the added lines per file and per kind (source, test, doc, generated). The snapshot is the only restore source. Then tell the user the count in one line, and continue without a wait: "The change adds N lines (S source, T tests). The cut starts now."
2. Read the rules and the decided behaviour
Read these and note their paths:
- The rules of the repo:
CLAUDE.md,AGENTS.md,CONTRIBUTING, docs about style, comments and tests, and the linter and type-checker config. - The sources of truth for the behaviour: the plan, spec, issue or PR text of this change; the text that the code shows or publishes (API descriptions, command-line help, docstrings that state a contract); and the tests that guard decided rules.
- The plans for later work: task lists, roadmaps, TODOs. They decide which unused functions stay.
- How to run the tests: the commands, the services they need (a database, a queue), and how to start a throwaway copy of each.
What ships with it
4 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.
- yesterday First seen · 196 lines · 52 tokens per session scan A bd9105802ec5
simpla is a skill published in the GitHub repository kBashar/myagentskills (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 2,854 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-10-29.
Other skills, from other repositories
Dotfiles
Manage /.zshrc and a chosen set of /.config/ directories (you name them in Config.md) against a private GitHub dotfiles repo. Intents: Push (verify private remote, scan secrets), Pull (clone/diff), Sync, Restore (timestamped backup), Status, Backup (local timestamped copy). Security scan blocks .env, secrets, tokens…
conventional-commit
Rules for writing Conventional Commits messages in this project. MUST be invoked every time a commit is created.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
ratchet-files
Ratchet source file size so every file stays small enough for an agent to read whole: find every file over a token budget, split oversized files by concept, and set up the pre-commit ratchet that stops them from growing. Use when a commit is blocked because a file is over the size budget, when asked to find or split…
git-guardrails-claude-code
A Claude Code setup that blocks selected destructive Git commands before they run. Git is a tool for tracking code changes; the blocked commands include pushing, deleting branches, discarding changes, and hard resets.