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 rjroy/vibe-garden --skill lintgit clone --depth 1 https://github.com/rjroy/vibe-gardenWrote 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/rjroy/vibe-garden/lint)<a href="https://agentmods.dev/skills/rjroy/vibe-garden/lint"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/lint/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/rjroy/vibe-garden/lint"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/lint.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.00055 | $0.01083 |
| Opus 5 | $0.00028 | $0.00541 |
| Sonnet 5 | $0.00011 | $0.00217 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
lint 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 9d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint
Health-check the wiki. Find what's broken, what's stale, what's drifted. Produce a report the maintainer can act on.
Steps
1. Load the index.
Read the field-guide index. Prefer .lore/reference/index.md; if it does not exist, read .lore/reference/index.html. Collect every local page link it lists — these are the indexed pages. Links may point to .md or .html files. If no index exists or the index contains no links, report that and stop.
2. Run five checks.
Run all five checks before reporting. Each check has a defined severity; do not promote or demote.
[error] Contradictions
Read every indexed wiki page in full. Pages may be Markdown or HTML. For HTML pages, use meta tags as metadata and visible body content as the page body. Look for pages that make conflicting claims about the same concept, entity, or decision. Two pages contradict each other when they assert incompatible facts about the same subject — not merely when they discuss it differently or at different levels of detail.
For each contradiction found, record:
- Both page paths
- The specific claim each page makes
- The subject they disagree on
[warning] Orphans
List every .md and .html file under .lore/reference/, recursively — stratified wikis keep pages in category subdirectories. Exclude index.md and index.html. Any file not listed in the index is an orphan.
For each orphan, record its path.
[warning] Stale sources
For each indexed wiki page, read its source metadata. Markdown pages use the fg-sources frontmatter field as a YAML list of relative paths. HTML pages use the fg-sources meta tag as a comma-separated or YAML-like list.
For each source path:
- Check whether the file exists on the filesystem.
- If it exists, compare its modification time against the wiki page's modification time.
- If the source is newer than the wiki page, the page is stale.
For each stale page:
- Set the
fg-statusfield tostale. For Markdown pages, update frontmatter. For HTML pages, update or add thefg-statusmeta tag. - Record the page path and which source files triggered the flag.
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.
- 9d ago First seen · 114 lines · 55 tokens per session scan A 33470194a571
lint is a skill published in the GitHub repository rjroy/vibe-garden (6 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 1,083 once invoked, about $0.0003 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-31.
Other skills, from other repositories
init-rpm
Project setup and verification. First run creates rpm context for a project. Repeat runs verify that an existing rpm setup matches the latest expected layout and apply safe migrations.
backlog
Manage the rpm backlog (long-term project tasks in docs/rpm/future/tasks.org — distinct from Claude's native TaskCreate list, which is session-scoped). Add, list, review, postpone, or complete entries. TRIGGER on natural-language backlog operations — phrasings like "backlog X", "add X to backlog", "add to backlog"…
version
Report the installed rpm plugin version. Use when the user asks for the rpm version, plugin version, installed version, or wants to verify which rpm release is loaded.
recursive-spine-scaffold
Use when a repo has (or is getting) the tracking stamp and needs the rest of its spine — interviews for and stamps up to six parts, each optional: a rules codex with a moments map, an ADR directory, a CI gate skeleton, a session-memory convention, a constraints file with its sha-pinned drift gate, and the loop…
recursive-spine-digest
Use when sweeping all recursive-spine-conforming repos for tracking health — aging deferrals (oldest first), stalled milestones, in-flight by lane, assigned-but-untouched issues, and debts named in closing comments but never filed, plus seedling pollen that never transplanted (hive repos). Reports honest denominators…
recursive-spine-bootstrap
Use when installing the recursive-spine tracking convention onto a repo — interviews for modules and dialect, then stamps labels, issue/PR templates, a CLAUDE.md/AGENTS.md tracking section, and cross-project board membership. Idempotent; degrades loudly on missing gh scopes; offers (never forces) plumb-line and…