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 marcoguillermaz/Tierward --skill commitgit clone --depth 1 https://github.com/marcoguillermaz/TierwardWrote 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/marcoguillermaz/tierward/commit)<a href="https://agentmods.dev/skills/marcoguillermaz/tierward/commit"><img src="https://agentmods.dev/badge/skills/marcoguillermaz/tierward/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/marcoguillermaz/tierward/commit"><img src="https://agentmods.dev/badge/skills/marcoguillermaz/tierward/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.00031 | $0.00986 |
| Opus 5.5 | $0.00012 | $0.00394 |
| Sonnet 5.5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00099 |
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 8d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When invoked, immediately execute Steps 1-6 below against the currently staged changes — do not ask what to work on, do not wait for a further instruction, do not treat this as reference material. Your job is to commit the already-staged work now. If nothing is staged, stop with the Step 1 message.
Step 1 - Read staged changes
Run:
git diff --cached --stat && git diff --cached
If the output is empty (nothing staged): respond "No staged files. Run git add <files> first." and stop.
Step 2 - Determine commit type
Classify based on staged files:
| Staged files | Type |
|---|---|
| Source code correcting broken behaviour | fix |
Test files only (__tests__/, e2e/, tests/, test_*.py, *_test.go, *Tests.swift, *Test.kt, *Test.java, src/test/) |
test |
Docs only (docs/, README.md) |
docs |
Context/config files (.claude/, CLAUDE.md, MEMORY.md, pipeline, skills, settings) |
chore |
| Restructuring without behaviour change | refactor |
When code + tests are staged together, type follows the code change (feat or fix).
BREAKING CHANGE: if a migration drops a column, renames a table, removes an API field, or changes a response shape - append ! after type/scope AND add a BREAKING CHANGE: footer line explaining the impact.
Step 3 - Determine scope
Derive from the primary functional area of the staged changes:
- Infrastructure:
auth·proxy·db·api·email - Horizontal:
ui(UI-only, no domain logic) ·context(pipeline.md, CLAUDE.md, skills, rules) - Omit scope if changes span >3 unrelated areas or are truly cross-cutting
Step 4 - Write description
Rules:
- Always write the commit message (subject and body) in English, regardless of the conversation or repository language
- Imperative mood:
add,fix,update,remove- never past tense - Max 72 characters total including
type(scope): - No period at end
Step 5 - Body (include when useful)
Include a body when:
- The reason for the change is non-obvious
- A BREAKING CHANGE needs explanation
- Phase 8 docs commit: list which doc files were updated and why
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.
- 8d ago Changed · +1 lines a788fd778cd5
- 1mo ago First seen · 96 lines · 31 tokens per session scan A 78bdbfdc62b7
commit is a skill published in the GitHub repository marcoguillermaz/Tierward (4 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 986 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-08-31.
Other skills, from other repositories
github-issue-to-pr
Implement one scafld-governed repository issue with normal host tools, prove the tested change through its finalize wall, and optionally publish the exact pull request through scoped provider authority with readback.
changelog-generator
Quick Reference - Parse conventional commits and generate categorized changelog.
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.
multiline-commit-messages
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.