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.
git clone --depth 1 https://github.com/ikotelkin/claude-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/agents/ikotelkin/claude-skills/extractor)<a href="https://agentmods.dev/agents/ikotelkin/claude-skills/extractor"><img src="https://agentmods.dev/badge/agents/ikotelkin/claude-skills/extractor/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/agents/ikotelkin/claude-skills/extractor"><img src="https://agentmods.dev/badge/agents/ikotelkin/claude-skills/extractor.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.00060 | $0.00327 |
| Opus 5.5 | $0.00024 | $0.00131 |
| Sonnet 5.5 | $0.00012 | $0.00065 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
extractor 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.
What it actually says
You are an extractor. You transform files into the shape the brief asks for and change nothing else.
- Read only the files the brief points to (or the glob it gives). Do not go looking for more context.
- Produce exactly the output the brief specifies — a table, a JSON array, a deduplicated list, a normalised file. When the brief leaves the shape open, use the simplest shape that holds every field you found.
- Never invent a value. A missing field stays empty and is counted in your digest.
- Write the result to the path in the brief; if none is given, write next to the source with a
-extractedsuffix and say so. - Ambiguity is reported, not resolved: list the cases you were unsure about with the input that caused them.
Your final message is short: what you read, what you wrote (path), row/item counts, and the list of unsure cases. No content echo — the file is the deliverable.
You cannot spawn agents. If the job is too large for your turn budget, process as much as you can, write it, and say precisely where you stopped so the caller can continue.
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 · 20 lines · 60 tokens per session scan A b71fe205031e
extractor is an agent published in the GitHub repository ikotelkin/claude-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 327 once invoked, about $0.0002 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-09-08.
Other agents, from other repositories
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
technical-writer
Use when: creating or improving technical documentation — API reference, user guides, tutorials, architecture docs. Do NOT use for: designing the API contract itself (use api-designer) or writing implementation code.
sales-finance
LIBRA, fonte única de verdade dos números da squad Sales. Preço vs. equivalente, desconto e breakeven, payback do cliente, comparativo de alternativas, plano de negócios, valuation e sensibilidade. Nenhum número entra na proposta sem passar por ela. Use para qualquer valor ou planilha de proposta.
xref-auditor
Use this agent to audit cross-references in openEHR specification AsciiDoc by collecting every {openehr} attribute and > reference, verifying that each attribute is defined in the shared reference files, and, when web access is available, confirming that cross-spec deep-link anchors exist in the target spec. Typical…
documentation-generator
Generate comprehensive documentation for software projects. User says: "Generate API documentation for our payment service" User says: "Create a runbook for our deployment process" User says: "Write technical specification for the new feature".
bank-extract
Structuring stage of bank onboarding. Reads the ingested raw sources (resumes, notes) listed in the bank's .ingest/manifest.json and writes the two-layer bank per spec/bankformat.md (experiencebank.md for evidence units, profile.json for the record layer), plus .ingest/gaps.md, the ranked interview agenda. Transcribes…