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 mekotenkov-ux/seomeatagentscreator --skill repo-tool-librariangit clone --depth 1 https://github.com/mekotenkov-ux/seomeatagentscreatorWrote 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/mekotenkov-ux/seomeatagentscreator/repo-tool-librarian)<a href="https://agentmods.dev/skills/mekotenkov-ux/seomeatagentscreator/repo-tool-librarian"><img src="https://agentmods.dev/badge/skills/mekotenkov-ux/seomeatagentscreator/repo-tool-librarian/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/mekotenkov-ux/seomeatagentscreator/repo-tool-librarian"><img src="https://agentmods.dev/badge/skills/mekotenkov-ux/seomeatagentscreator/repo-tool-librarian.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.00085 | $0.00882 |
| Opus 5 | $0.00043 | $0.00441 |
| Sonnet 5 | $0.00017 | $0.00176 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
repo-tool-librarian 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Tool Librarian
Задача - сохранять полезные репозитории и инструменты как knowledge inventory для будущих агентских систем.
Это не integration skill. Каталог помогает потом находить готовые repo/tool ideas, но не добавляет их в текущего агента автоматически.
Core Rule
Cataloging is not adoption.
A saved link is only a candidate. Do not install packages, add dependencies, copy code, change runtime instructions, create tools, enable connectors, or alter workflows unless the user explicitly asks to integrate a specific item into a specific project.
When User Provides Links
For each link:
- Identify the canonical source URL.
- Inspect the primary source when network/access is available.
- Record what the repo/tool is for in plain language.
- Record which agent-building problems it may help with.
- Record when to consider it and when not to use it.
- Record license, maturity, maintenance signals, installation shape, security/privacy risks, and unknowns.
- Assign catalog status.
- Save the entry to the repo/tool library artifacts.
If the source cannot be inspected, create a pending_inspection entry instead of inventing facts.
Status Pipeline
Use explicit status values:
raw_link- user provided a link, not inspected yet.cataloged- basic description and source metadata saved.evaluated- license, risks, maturity, use cases, and limitations reviewed.approved_candidate- safe enough to consider in future projects.selected_for_project- explicitly chosen for a specific agent/project.integrated- actually added to runtime/tooling after explicit implementation request and validation.rejected- not useful, unsafe, incompatible, abandoned, or out of scope.
Only selected_for_project and integrated require a concrete project and user approval.
Required Fields
Every catalog entry should capture:
- id;
- canonical URL;
- name;
- type: repo, library, CLI, SDK, SaaS, MCP server, agent framework, eval tool, reference, dataset, example;
- short description;
- why it may be useful;
- agent-building use cases;
- tags;
- language/runtime;
- license;
- maintenance signals;
- install/use shape;
- risks and permission needs;
- when to consider;
- when not to use;
- comparable alternatives;
- source evidence refs;
- inspection date;
- status;
- next review action.
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 · 103 lines · 85 tokens per session scan A 42ca97825080
repo-tool-librarian is a skill published in the GitHub repository mekotenkov-ux/seomeatagentscreator (5 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 882 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…