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 TSS-Blue-AI-Lab/ai-lab-agent-skills --skill resolve-docsgit clone --depth 1 https://github.com/TSS-Blue-AI-Lab/ai-lab-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/tss-blue-ai-lab/ai-lab-agent-skills/resolve-docs)<a href="https://agentmods.dev/skills/tss-blue-ai-lab/ai-lab-agent-skills/resolve-docs"><img src="https://agentmods.dev/badge/skills/tss-blue-ai-lab/ai-lab-agent-skills/resolve-docs/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/tss-blue-ai-lab/ai-lab-agent-skills/resolve-docs"><img src="https://agentmods.dev/badge/skills/tss-blue-ai-lab/ai-lab-agent-skills/resolve-docs.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.00078 | $0.01794 |
| Opus 5 | $0.00039 | $0.00897 |
| Sonnet 5 | $0.00016 | $0.00359 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
resolve-docs 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 148 lines · 78 tokens per session scan A c2aba1aebdc8
resolve-docs is a skill published in the GitHub repository TSS-Blue-AI-Lab/ai-lab-agent-skills (24 stars, last pushed 1mo ago), with no licence file. It adds 78 tokens to every session and 1,794 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
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why. Also the place for complaints, feedback and settings changes about this skill itself.
review
Adversarial fresh-context review of an increment before it ships. Every finding cites path:line and is re-verified. Use when saying "review", "grill this", or "critique the implementation".
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
summarize
A guide for turning conversations, logs, documents, or investigation notes into short, action-oriented summaries. It requires conclusions to be tied to available evidence and distinguishes confirmed facts from items still needing confirmation.
pre-modification-check
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.