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 danielrosehill/Claude-Taxonomy-Creation-Plugin --skill export-formatsgit clone --depth 1 https://github.com/danielrosehill/Claude-Taxonomy-Creation-PluginWrote 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/danielrosehill/claude-taxonomy-creation-plugin/export-formats)<a href="https://agentmods.dev/skills/danielrosehill/claude-taxonomy-creation-plugin/export-formats"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-taxonomy-creation-plugin/export-formats.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.00036 | $0.00539 |
| Opus 5 | $0.00018 | $0.00269 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
export-formats 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 8d 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
Export Taxonomy to Multiple Formats
Export a generated taxonomy to CSV, TSV, JSON, NDJSON, SQL, or YAML. Preserve all columns and metadata.
When to use
- "Export this as JSON for my app"
- "I need a SQL seed file with INSERT statements"
- "Give me NDJSON for BigQuery"
- "Convert to YAML format"
Inputs to gather
- Taxonomy file path: Absolute path to generated CSV or JSON (auto-discover from
data/<name>/if not given). - Format: CSV, TSV, JSON, NDJSON, SQL, YAML.
- For SQL format: Table name (inferred from filename if not given).
Procedure
- Read the taxonomy file (CSV or JSON).
- Normalize to in-memory structure (list of dicts, one per row).
- Write to
data/<name>/exports/in the requested format:- CSV: Standard
csvmodule; preserve headers. - TSV:
csvwithdelimiter='\t'. - JSON: Pretty-printed array of objects; include schema hint in a
_schemafield if needed. - NDJSON: One JSON object per line (no array wrapper); good for streaming/BigQuery.
- SQL: Generate
CREATE TABLEDDL +INSERTstatements. Include the same DDL asload-to-postgresskill (infer types from data); wrap in a transaction (BEGIN; ... COMMIT;). - YAML: Array of objects in YAML syntax (each entry as a dict with key-value pairs).
- CSV: Standard
- Log the export: write filename and format to
state/exports/<timestamp>-<name>-<format>.log. - Report to user: file size, row count, format name, full output path.
Output / side effects
- Exported file in
data/<name>/exports/<name>.<ext>where ext is csv, tsv, json, ndjson, sql, yaml. - Export logged to
state/exports/<timestamp>-<name>-<format>.log.
Safety / constraints
- No credentials in SQL: SQL seed files should not include connection strings or credentials.
- Reversible: Export does not modify the original taxonomy; purely additive.
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.
- 8d ago First seen · 46 lines · 36 tokens per session scan A 1c8aab4f290f
export-formats is a skill published in the GitHub repository danielrosehill/Claude-Taxonomy-Creation-Plugin (3 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 539 once invoked, about $0.0002 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…