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 Green-PT/honey-for-devs --skill honey-debtgit clone --depth 1 https://github.com/Green-PT/honey-for-devsWrote 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/green-pt/honey-for-devs/honey-debt)<a href="https://agentmods.dev/skills/green-pt/honey-for-devs/honey-debt"><img src="https://agentmods.dev/badge/skills/green-pt/honey-for-devs/honey-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/green-pt/honey-for-devs/honey-debt"><img src="https://agentmods.dev/badge/skills/green-pt/honey-for-devs/honey-debt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.00435 |
| Opus 5 | $0.00007 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
honey-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 12d 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
Honey Debt
Lever 1 trades code for a known ceiling. That trade is only honest if someone can
see it later. Every deliberate simplification carries a honey: comment naming its
ceiling and the trigger to revisit; this collects them into one ledger.
Scan
grep -rnE '(#|//|--|/\*) ?honey:' . --exclude-dir={node_modules,.git,dist,build,vendor}
Each hit is one row. The comment prefix is what keeps prose that merely mentions the convention out of the ledger.
Output
One row per marker, grouped by file:
<file>:<line> — <what was simplified>. ceiling: <the limit>. trigger: <when to revisit>.
The convention is honey: <ceiling>, <trigger>, so both fields come straight from
the comment. Add git blame -L<line>,<line> -- <file> per row only if the user asks
who owns it.
Tag any marker with no trigger no-trigger — a ceiling without a revisit condition
is the shape that rots. End with:
<N> markers, <M> with no trigger.
Nothing found: No honey: debt. Clean ledger.
Boundaries
- Report only. Don't fix, refactor, or remove markers — the user decides what to pay down. Offer, don't act.
- Don't invent debt. A
TODO/FIXMEis not ahoney:marker; mention the count separately at most once if it's large, don't fold it into the ledger. - Don't editorialise per row. The ledger is data. Save any judgement for one closing line, and only if something is genuinely alarming.
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.
- 12d ago First seen · 52 lines · 14 tokens per session scan A 5a3b6eba6b3e
honey-debt is a skill published in the GitHub repository Green-PT/honey-for-devs (295 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 435 once invoked, about $0.0001 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
code-review-excellence
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
review-diff
Scan git diffs for project-specific anti-patterns. Triggers on: 'scan diff', 'check diff', 'anti-pattern check', 'pattern scan', 'review changes'.
review-full
Run a comprehensive multi-perspective code review on recent changes. Also triggers on 'is this secure?', 'security review', 'check for vulnerabilities', 'could this be exploited?' for security-focused review. Produces: GO/NO-GO verdict + findings table (Severity | Category | File:Line | Issue | Recommendation)…
pr-review
Review and post feedback on a GitHub or Gitea pull request end-to-end: fetch the PR diff, run a multi-agent code review, and auto-post the verdict as a real PR review (approve/request-changes/comment) via the platform's API. Triggers on: 'review this PR', 'review PR #N', 'check this pull request', 'post a PR review'…
prereview
Review the current diff against this team's conventions and invariants before it ships. Invoke with /prereview before opening a PR, or run as a pre-push gate.