Borrowing it
Nothing to install: this file belongs to susomejias/rembric. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/susomejias/rembric/main/.agents/skills/zero-tech-debt/SKILL.mdgit clone --depth 1 https://github.com/susomejias/rembricWrote 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/susomejias/rembric/zero-tech-debt)<a href="https://agentmods.dev/skills/susomejias/rembric/zero-tech-debt"><img src="https://agentmods.dev/badge/skills/susomejias/rembric/zero-tech-debt/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/susomejias/rembric/zero-tech-debt"><img src="https://agentmods.dev/badge/skills/susomejias/rembric/zero-tech-debt.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.00074 | $0.00395 |
| Opus 5 | $0.00037 | $0.00198 |
| Sonnet 5 | $0.00015 | $0.00079 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
zero-tech-debt 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.
What it actually says
Zero Tech Debt
Reshape the change from the intended end state, not from the historical path that produced the current patch. The goal is the code that should exist now, not the smallest diff from what's there.
Steps
-
Name the end state. In one or two sentences, describe the product surface and architecture as if you were building it today.
-
Find real callers before preserving anything. Grep for actual usage of each mode, prop, wrapper, route alias, or fallback. If nothing references it, delete it — do not "improve" it.
-
Reshape around the final surface. Prefer one clear component or flow over mode flags. Split only when there is an obvious boundary: state, layout, controls, or domain commands.
-
Move shared rules to one place. Feature flags, permissions, route gating, URL state, and command naming must not be duplicated across pages or buried inside view components.
-
Verify the intended flow. Test the new behavior and the assumptions you deleted — anything that touched navigation, permissions, or persisted state.
Rules
- Optimize for the code that should exist, not the smallest diff from the old shape.
- Delete dead compatibility paths instead of polishing them.
- Do not invent a generic framework for a single feature.
- Keep the refactor scoped to what makes the final shape coherent — no opportunistic cleanup.
- Prefer names that describe product intent over implementation history.
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 · 30 lines · 74 tokens per session scan A c40424d5a987
zero-tech-debt is a skill published in the GitHub repository susomejias/rembric (12 stars, last pushed 8d ago), licensed MIT. It adds 74 tokens to every session and 395 once invoked, about $0.0004 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-30.
Other skills, from other repositories
hunt-nodejs
Hunt Node.js specific vulnerabilities — Prototype Pollution → RCE chains (lodash/merge/assign), Express trust proxy misconfiguration, childprocess/eval injection, template engine SSTI (EJS/Pug/Handlebars), path traversal in file servers, require() injection, environment variable exfil via /proc/self/environ. Use when…
codex-auth-setup
Install or refresh codex-multi-auth for the official Codex CLI, run first login, and verify account health and routing.
marm-init
Guided MARM MCP setup. Invoke after running marm-memory init on the CLI to configure MARM memory across your agent. Drives transport choice, runtime choice, MCP config writing, multi-agent linking, and server start. Works on Claude, Codex, Gemini, Qwen, Cursor, VS Code, and other MCP-capable agents.
example
Example fixture skill for scanner regression coverage.
kanban-orchestrator
Kanban orchestrator: decompose, route, verify. No executing.
codex-memory-trim
A procedure for managing Codex's global memory, including removing duplicates, shortening verbose entries, and adding user-defined rules or preferences.