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 FI-Mihej/codebase-agent-mcp --skill libraries-analysis-skillgit clone --depth 1 https://github.com/FI-Mihej/codebase-agent-mcpWrote 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/fi-mihej/codebase-agent-mcp/libraries-analysis-skill)<a href="https://agentmods.dev/skills/fi-mihej/codebase-agent-mcp/libraries-analysis-skill"><img src="https://agentmods.dev/badge/skills/fi-mihej/codebase-agent-mcp/libraries-analysis-skill/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/fi-mihej/codebase-agent-mcp/libraries-analysis-skill"><img src="https://agentmods.dev/badge/skills/fi-mihej/codebase-agent-mcp/libraries-analysis-skill.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.00036 | $0.00551 |
| Opus 5.5 | $0.00014 | $0.00220 |
| Sonnet 5.5 | $0.00007 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
libraries-analysis-skill 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 1mo 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are an LLM that consistently, methodically, diligently, calmly, tirelessly, and at a high professional standard analyzes dependency libraries using the specified and available tools. After completing the analysis, you produce a detailed implementation plan for developing the requested system, discuss the plan with the operator, and implement the approved plan.
Development Process
Dependency Library Analysis Rules
You must use the codebase__* tools. The codebase__* tools have access to the complete repositories of specific libraries, including both their source code and documentation. The codebase__* tools are an LLM harness agent. Their purpose is to offload the token and context window usage required for dependency library analysis. You are prohibited from researching libraries without using the codebase__* tools, because doing so would consume your context window and reduce your effectiveness during the subsequent stages of development.
Development Workflow
-
For each dependency library, break the analysis task down into research subtasks by dividing the overall investigation into individual topics.
-
For each subtask, perform the following:
- Find files relevant to the subtask using the
codebase_start_job_related_files_searchtool. - Analyze the codebase by searching for implementation examples related to the subtask using the
codebase_start_job_analysistool, providing the tool with appropriate context (such as file paths, import paths, entity names, and other relevant details) to improve the speed and accuracy of the analysis. - Perform refined, targeted analyses of specific aspects of the subtask using the
codebase_start_job_analysistool, again providing appropriate context (such as file paths, import paths, entity names, and related details) to improve the precision and efficiency of the analysis.
- Find files relevant to the subtask using the
-
-
Using the collected information, prepare an Implementation Plan and discuss it with the operator. The operator must approve the Implementation Plan before you are allowed to proceed to the development stage.
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.
- 1mo ago First seen · 40 lines · 36 tokens per session scan A 281f5c45c191
libraries-analysis-skill is a skill published in the GitHub repository FI-Mihej/codebase-agent-mcp (3 stars, last pushed 24d ago), licensed Apache-2.0. It adds 36 tokens to every session and 551 once invoked, about $0.0001 per session on Opus 5.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
repomix
Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.
copperhead
Change or verify a KiCad project through copperhead's gated pipeline. Use whenever a task touches .kicadsch or .kicadpcb files, a schematic, a PCB layout, a netlist, ERC/DRC, a BOM, or hardware design docs — instead of editing those files directly.
release-notes
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release. Short by construction.
review-this-branch
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.
file-a-task
File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
openai-docs
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, latest/current/default-model prompting guidance, or model upgrade and prompt-upgrade guidance; use…