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 agentmods add skills/id-andyyy/labai/lab-helpnpx skills add id-andyyy/LabAI --skill lab-helpgit clone --depth 1 https://github.com/id-andyyy/LabAIWrote 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/id-andyyy/labai/lab-help)<a href="https://agentmods.dev/skills/id-andyyy/labai/lab-help"><img src="https://agentmods.dev/badge/skills/id-andyyy/labai/lab-help.svg" alt="Measured on agentmods" 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.00010 | $0.00255 |
| Opus 5 | $0.00005 | $0.00128 |
| Sonnet 5 | $0.00002 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
lab-help 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 5d 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
Пользователь выполняет инструкцию из instructions.md и столкнулся с проблемой.
Что делать
- Прочитай
.claude/lab/config.jsonдля контекста (ОС пользователя, тип работы, дополнительные данные). - Прочитай
instructions.md,.claude/lab/assignment.md,.claude/lab/source-material.md(полный текст исходного документа) и файлы в.claude/lab/reference-docs/(дополнительная теория по работе) чтобы понимать контекст. - Разберись в проблеме пользователя (описана ниже).
- Ответь на вопрос в чате — объясни, что пошло не так и как решить.
- Если нужно изменить instructions.md:
- Обнови соответствующие пункты.
- Помечай новые/изменённые пункты символом ⚠️ в начале строки.
- Сообщи в чате, какие именно пункты были изменены.
- Если для ответа не хватает знаний — выполни поиск в интернете. Не выдумывай.
Проблема пользователя
$ARGUMENTS
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.
- 5d ago First seen · 23 lines · 10 tokens per session scan A c6ea2f141754
lab-help is a skill published in the GitHub repository id-andyyy/LabAI (3 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 255 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-31.
Other skills, from other repositories
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
offensive-exploit-dev-course
Full exploit development course roadmap and syllabus: weekly topics, recommended reading, lab setup, and learning path from vulnerability classes through advanced exploitation. Use to structure exploit dev training or onboard new researchers.
explain-this
Explain whatever the user is pointing at right now in plain language: a pending question, a piece of code, an error, a command output, or an artifact like a plan or findings report. Use when the user asks to "explain this", "what am I being asked", "what's happening right now", "help me understand this", "what does…
understand-change
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed"…
ape-quiz-me
Quizzes you on content you claim to have read -- Socratic, one question at a time, hints that narrow but never reveal. Ends with a verdict on what you understood versus merely recited. Trigger on "ape quiz me", "quiz me on this", "test my understanding", "did I actually get this", or any request to be tested on shared…
ape-write-pseudocode
Guidelines for writing pseudocode for functions and algorithms. Use this skill whenever the user asks to write pseudocode, sketch out an algorithm, or describe the logic of a function at a high level. Trigger on phrases like "write pseudocode", "sketch this algorithm", "pseudocode for this function", or "describe the…