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 agentmods add agents/stonematt/mcp-obsidian-cli/triage-labelsgit clone --depth 1 https://github.com/stonematt/mcp-obsidian-cliWrote 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/stonematt/mcp-obsidian-cli/triage-labels)<a href="https://agentmods.dev/agents/stonematt/mcp-obsidian-cli/triage-labels"><img src="https://agentmods.dev/badge/agents/stonematt/mcp-obsidian-cli/triage-labels.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.00000 | $0.00853 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
triage-labels 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 6d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Labels
The engineering skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo, which follow the nitimini lifecycle vocabulary.
Canonical role → repo label mapping
| Role in skills | Repo label(s) | Meaning |
|---|---|---|
needs-triage |
status: triage |
New issue, needs scoping. All issues open here. |
needs-info |
status: needs-info |
Waiting on the reporter for clarification. |
ready-for-agent |
status: ready + afk-ready flag |
Spec'd, scope tight enough that an AFK agent (Sonnet, no human pings, very low uncertainty) can pick it up. |
ready-for-human |
status: ready (no afk-ready) |
Spec'd but needs human implementation — too much uncertainty for AFK. |
wontfix |
close with --reason "not planned" |
Declined. No label; the closed state is the signal. |
When a skill says "apply the AFK-ready label," apply BOTH status: ready AND afk-ready. The flag is orthogonal to status, per nitimini.
Full lifecycle label set
Beyond the five triage roles, the issue state machine uses more labels. See issue-tracker.md and the nitimini workflow for the full state machine.
| Namespace | Label | Meaning |
|---|---|---|
| status (lifecycle) | status: triage |
New, needs scoping |
| status | status: needs-info |
Waiting on reporter |
| status | status: ready |
Spec'd, awaiting pickup |
| status | status: wip |
Branch open, work started |
| status | status: blocked |
Waiting on dependency or decision |
| status | status: staged |
Merged to dev, awaiting prod release |
| (project) | Released |
Project Status only (no label); set on close by workflow |
| flag | afk-ready |
Brief tight enough for autonomous-agent pickup. Orthogonal to status:*. |
| flag | kind:bse |
Bug or small enhancement; opportunistic / throw-in work |
| flag | priority: high |
Escalate scheduling |
| intent | intent:structural |
Refactor with no user-visible change. Snapshot diff must be empty. |
| reference | adr |
Issue references or proposes an ADR |
| area | area:* |
Code area scope. Deferred — create on first use. |
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.
- 6d ago First seen · 59 lines · 0 tokens per session scan A 1325cd2d8f0c
triage-labels is an agent published in the GitHub repository stonematt/mcp-obsidian-cli (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 853 tokens. 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 agents, from other repositories
vault-explorer
Use proactively when researching what the vault knows about a topic, before creating new notes, or when exploring existing knowledge and connections. Run in foreground — results inform the caller's next steps. Examples: Context: User asks about a topic before creating new content. user: "What does the vault already…
coder
Sonnet implementer for a well-scoped change — edits/tests to green; not architecture calls, asks if ambiguous.
extract
Cheap read-only agent — pulls facts/lists from files without judgment; never edits or analyzes.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
ios-tester
You are an iOS testing agent for the Bullhorn project — a Next.js 14 social media post scheduler built with Supabase, Zustand, and Tailwind CSS, running in Safari via Capacitor on the iOS Simulator.
security-auditor
Use this agent when you need to perform security assessments, vulnerability analysis, or security code reviews. Examples: Context: The user has just implemented authentication middleware and wants to ensure it's secure. user: 'I just added JWT authentication to my API. Can you review it for security issues?'…