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 aidi1723/safe-agent-skills --skill engineering-tech-debt-tracker-reviewgit clone --depth 1 https://github.com/aidi1723/safe-agent-skillsWrote 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/aidi1723/safe-agent-skills/engineering-tech-debt-tracker-review)<a href="https://agentmods.dev/skills/aidi1723/safe-agent-skills/engineering-tech-debt-tracker-review"><img src="https://agentmods.dev/badge/skills/aidi1723/safe-agent-skills/engineering-tech-debt-tracker-review/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/aidi1723/safe-agent-skills/engineering-tech-debt-tracker-review"><img src="https://agentmods.dev/badge/skills/aidi1723/safe-agent-skills/engineering-tech-debt-tracker-review.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.00355 |
| Opus 5.5 | $0.00013 | $0.00142 |
| Sonnet 5.5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
engineering-tech-debt-tracker-review 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 1mo 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.
This is a copy
72% identical to business-code-to-prd-review — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Tech Debt Tracker Review
When To Use
Use this draft when reviewing the tech-debt-tracker metadata-only
candidate from claude-skills before deciding whether to author a local
OneCode skill, merge it into an existing skill, or keep it reference-only.
Safe Workflow
- Identify the task, audience, owner, source domain, target catalog category, and expected artifact.
- Compare the candidate with existing trusted Safe-Agent-Skills to avoid duplicate or overlapping guidance.
- Draft local OneCode guidance from project requirements and operator review; do not copy upstream skill bodies.
- Check provenance, license notes, runtime permissions, and connector assumptions before import.
- Produce an adoption recommendation only; Do not execute upstream content or mark this draft trusted.
Expected Output
- metadata-only candidate summary
- overlap and merge recommendation
- local authoring notes
- required verifier checklist
- adoption decision: convert, merge, keep reference-only, or reject
Verifier Expectations
- metadata-only boundary check
- duplicate skill check
- provenance and license check
- import, serial approval, schema-check, maintain-check, and verify before trust
Draft Metadata
- upstream candidate:
tech-debt-tracker - source domain:
engineering - source path:
engineering/skills/tech-debt-tracker - mapped category:
engineering - score:
41 - priority:
P3 - adoption before draft:
reference_only
What ships with it
1 file 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.
- 1mo ago First seen · 51 lines · 33 tokens per session scan A 61cb93f113e7
engineering-tech-debt-tracker-review is a skill published in the GitHub repository aidi1723/safe-agent-skills (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 355 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 72% identical to business-code-to-prd-review, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…