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 alebgl77/tierdecay --skill tierdecay-executiongit clone --depth 1 https://github.com/alebgl77/tierdecayWrote 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/alebgl77/tierdecay/tierdecay-execution)<a href="https://agentmods.dev/skills/alebgl77/tierdecay/tierdecay-execution"><img src="https://agentmods.dev/badge/skills/alebgl77/tierdecay/tierdecay-execution/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/alebgl77/tierdecay/tierdecay-execution"><img src="https://agentmods.dev/badge/skills/alebgl77/tierdecay/tierdecay-execution.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.00039 | $0.00269 |
| Opus 5.5 | $0.00016 | $0.00108 |
| Sonnet 5.5 | $0.00008 | $0.00054 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
tierdecay-execution 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 13d 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.
What it actually says
TierDecay execution standards
- Implement exactly the brief: smallest diff that satisfies ACCEPTANCE. No drive-by refactors, no new dependencies unless allowed.
- Read every file in FILES before editing. Neighbouring code is the style guide.
- Prove it: run the narrowest test command covering ACCEPTANCE; paste the command and the tail of its output.
- Ambiguity or a design decision → stop and return
BLOCKED: <what> / <why> / <2–3 options>. - Never write
.tierdecay/,.claude/,.codex/, or.agents/. Report playbook feedback instead:PLAYBOOK: PB-<n> applied → pass|fail, orPB-<n> stale: <why>when the entry contradicts the code. Never update hits or counters yourself. - Report: CHANGES (one line per file) · TESTS · DEVIATIONS (must be empty) · PLAYBOOK · BLOCKERS.
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.
- 13d ago First seen · 22 lines · 39 tokens per session scan A b18db5007cd9
tierdecay-execution is a skill published in the GitHub repository alebgl77/tierdecay (1 stars, last pushed 8d ago), licensed MIT. It adds 39 tokens to every session and 269 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-02.
Other skills, from other repositories
compile-basic
Basic compiler conformance fixture.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
verification-loop
A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…