superspecs: Skill for Claude Code

.skills/tag-taxonomy/SKILL.md

tag-taxonomy is a skill for Claude Code, Codex from fokkerone/superspecs. It costs 62 tokens per session (1,077 once invoked), scanned A, original, MIT.

A tag-maintenance skill for an Obsidian wiki vault, where tags group related notes. It keeps one approved name for each concept.

In plain words
What is it for?
Creating or updating the approved tag list, finding non-approved tags, and changing wiki pages to use the approved names.
Why use it?
It stops similar tags such as “auth” and “authentication” from splitting related notes into separate groups.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is fokkerone/superspecs's own configuration. It tells Claude Code and Codex how to work on superspecs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything superspecs configures →

Reuse

Borrowing it

Nothing to install: this file belongs to fokkerone/superspecs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/fokkerone/superspecs/main/.skills/tag-taxonomy/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/fokkerone/superspecs

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for tag-taxonomy

README.md
[![agentmods](https://agentmods.dev/badge/skills/fokkerone/superspecs/tag-taxonomy/github.svg)](https://agentmods.dev/skills/fokkerone/superspecs/tag-taxonomy)
Your own site
<a href="https://agentmods.dev/skills/fokkerone/superspecs/tag-taxonomy"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/tag-taxonomy/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.

agentmods 80×15 button for tag-taxonomy

Your own site · 80×15
<a href="https://agentmods.dev/skills/fokkerone/superspecs/tag-taxonomy"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/tag-taxonomy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,077 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.01077
Opus 5 $0.00031 $0.00539
Sonnet 5 $0.00012 $0.00215
Haiku 4.5 $0.00006 $0.00108

Measured 10d ago against content hash 3f73fa268e78, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

tag-taxonomy 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 10d 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.

.skills/tag-taxonomy/SKILL.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: tag-taxonomy

You are maintaining tag consistency across the wiki vault.

Tags are how the Obsidian graph clusters knowledge. Without a controlled vocabulary, tags drift: "auth" and "authentication" and "Authorization" end up meaning the same thing, fragmenting the graph. This skill enforces one canonical tag per concept.


The Taxonomy File

superspec/wiki/_meta/taxonomy.md is the source of truth for canonical tags.

Format:

---
title: Tag Taxonomy
updated: <YYYY-MM-DD>
---

# Tag Taxonomy

Canonical tag vocabulary for this vault. All wiki pages must use tags from this list.
Add new tags here before using them in pages.

## Domain Tags
<!-- One tag per domain folder -->
- `auth` — authentication and authorization
- `api` — API design and contracts
- `data` — data models and storage
- `ui` — frontend and interface
- `infra` — infrastructure and deployment
- `patterns` — reusable implementation patterns
- `decisions` — architecture decision records

## Topic Tags
<!-- Cross-domain concept tags -->
- `jwt` — JSON Web Tokens
- `caching` — caching strategies and implementations
- `error-handling` — error handling patterns
- `testing` — test strategy and patterns
- `performance` — performance considerations
- `security` — security concerns

## Meta Tags
<!-- Reserved for wiki structure -->
- `index` — index and home pages (do not use in content pages)
- `log` — activity log (reserved)
- `insights` — generated insights pages
- `lint` — lint report pages
- `query-derived` — pages created from wiki-query results
- `capture` — pages created from wiki-capture

## Aliases
<!-- Non-canonical → canonical mappings -->
- `authentication` → `auth`
- `authorization` → `auth`
- `Authorization` → `auth`
- `caches` → `caching`
- `errors` → `error-handling`

Steps

Mode A — Init (first run, no taxonomy yet)

If superspec/wiki/_meta/taxonomy.md does not exist:

  1. Scan all wiki pages and collect every tag in use
  2. Group by apparent intent (cluster similar tags)
  3. For each cluster, pick the shortest, clearest, lowercase-hyphenated canonical form
  4. Write _meta/taxonomy.md with:
    • Domain tags (one per domain folder)
    • Topic tags (all unique concepts found)
    • Alias map (non-canonical → canonical for each cluster)
  5. Report what was found and the proposed taxonomy — wait for confirmation before normalizing pages

Read the full file on GitHub · 142 lines

Changes

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.

  1. 10d ago First seen · 142 lines · 62 tokens per session scan A 3f73fa268e78

Subscribe to this mod's changes

tag-taxonomy is a skill published in the GitHub repository fokkerone/superspecs (4 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,077 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens