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 saski/arnesto --skill tag-taxonomygit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/tag-taxonomy)<a href="https://agentmods.dev/skills/saski/arnesto/tag-taxonomy"><img src="https://agentmods.dev/badge/skills/saski/arnesto/tag-taxonomy.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.00115 | $0.01600 |
| Opus 5 | $0.00057 | $0.00800 |
| Sonnet 5 | $0.00023 | $0.00320 |
| Haiku 4.5 | $0.00012 | $0.00160 |
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 4d 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.
This is a copy
88% identical to tag-taxonomy — 37 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tag Taxonomy — Controlled Vocabulary for Wiki Tags
You are enforcing consistent tagging across the wiki by normalizing tags to a controlled vocabulary.
Before You Start
- Read
.envto getOBSIDIAN_VAULT_PATH - Read
$OBSIDIAN_VAULT_PATH/_meta/taxonomy.md— this is the canonical tag list - Read
index.mdto understand the wiki's scope
The Taxonomy File
The canonical tag vocabulary lives at $OBSIDIAN_VAULT_PATH/_meta/taxonomy.md. It defines:
- Canonical tags — the tags that should be used
- Aliases — common alternatives that should be mapped to the canonical form
- Rules — max 5 tags per page, lowercase/hyphenated, prefer broad over narrow
- Migration guide — specific renames for known inconsistencies
Always read this file before tagging. It's the source of truth.
Reserved System Tags
visibility/ is a reserved tag group with special rules. These tags are not domain or type tags and are managed separately from the taxonomy vocabulary:
| Tag | Purpose |
|---|---|
visibility/public |
Explicitly public — shown in all modes (same as no tag) |
visibility/internal |
Team-only — excluded in filtered query/export mode |
visibility/pii |
Sensitive data — excluded in filtered query/export mode |
Rules for visibility/ tags:
- They do not count toward the 5-tag limit
- Only one
visibility/tag per page - Omit entirely when content is clearly public — no tag needed
- Never add
visibility/internaljust because content is technical; use it only for genuinely team-restricted knowledge - When running a tag audit, report
visibility/tag usage separately — do not flag them as unknown or non-canonical
When normalizing tags, leave visibility/ tags untouched — they are not subject to alias mapping.
Mode 1: Tag Audit
When the user wants to see the current state of tags:
Step 1: Scan all pages
Glob: $VAULT_PATH/**/*.md (excluding _archives/, .obsidian/, _meta/)
Extract: tags field from YAML frontmatter
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.
- 4d ago First seen · 184 lines · 115 tokens per session scan A 90a69fafc9de
tag-taxonomy is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed yesterday), licensed Unlicense. It adds 115 tokens to every session and 1,600 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to tag-taxonomy, differing in 37 lines, and is treated as a copy.
Other skills, from other repositories
orbit-general
Open Orbit briefing skill — selected by the Orbit pipeline when the user has two or more connectors connected. Pulls the past 24 hours of activity from every authenticated connector (GitHub, Linear, Notion, Slack, 飞书, Calendar, Gmail, Drive, Sentry, Vercel, …) and renders a single adaptive bento-grid dashboard at the…
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
discovery-question-form
Structured clarification form for unresolved material requirements.
mailbox
A guide for performing email and mailbox tasks through the QwenPaw mailbox system. It covers supported personal email providers, credentials, configuration, and the required mailbox workflow.
channel_message
Use this skill to proactively send a one-way message to a user/session/channel, usually only when the user explicitly asks to send to a channel/session or when proactive notification is needed. First query sessions with qwenpaw chats list, then push with qwenpaw channels send.
ask-matt
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.