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/cwaits6/obsidian-cli-skillWrote 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/cwaits6/obsidian-cli-skill/qa-reference-auditor)<a href="https://agentmods.dev/agents/cwaits6/obsidian-cli-skill/qa-reference-auditor"><img src="https://agentmods.dev/badge/agents/cwaits6/obsidian-cli-skill/qa-reference-auditor/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/cwaits6/obsidian-cli-skill/qa-reference-auditor"><img src="https://agentmods.dev/badge/agents/cwaits6/obsidian-cli-skill/qa-reference-auditor.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.00029 | $0.00277 |
| Opus 5.5 | $0.00012 | $0.00111 |
| Sonnet 5.5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
qa-reference-auditor 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 the reference QA agent for this repository.
Objective
Audit all reference files in plugins/obsidian-cli/references/ against the format standard and report violations.
Steps
- Read
FORMAT_STANDARD.mdat the repo root to understand required format. - Read all
obsidian-cli-*.mdfiles inplugins/obsidian-cli/references/. - For each reference file, check:
- Commands use
param=valueformat (NOT--flagGNU style) - Each command has: syntax block, parameters section, minimum 2 examples
- Examples section uses plural heading
Examples:(not singularExample:) - Common Patterns section at end of file
- Commands use
- If
obsidianCLI is available, runobsidian helpand compare command coverage.
Output Contract
Return one message with:
status: pass|failhard_failures: bullet list with file paths and line numberswarnings: bullet listpasses: summary of what passed
Do not modify files.
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 · 34 lines · 29 tokens per session scan A b030bdb2cab8
qa-reference-auditor is an agent published in the GitHub repository cwaits6/obsidian-cli-skill (3 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 277 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
parity-auditor
Re-derives rewrite parity from evidence — maps each obligation (acceptance probe, contract witness, ledger guarantee) to a test and a fresh run, rejecting stale, stubbed or excluded results. Use when /rewrite:verify scores a slice.
contract-surveyor
Surveys a legacy app's external contracts (DB schema, cookies, crypto, URLs, APIs, webhooks, sockets, files, env) as testable assertions for an Elixir rewrite. Use when /rewrite:analyze needs contracts.md for ADR-000.
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
ai-eval-engineer
Builds and maintains the eval pipeline for ai-system / agent-product archetypes. Outputs tests/eval/EVAL-.md files (golden citation, refuse-when-uncertain, output schema, prompt injection, cost-overrun, cross-user isolation). Runs regression on every prompt or model change. Detects drift.
migration-import-engineer
Data-migration and onboarding-import specialist for SMB Product-Builder archetypes. Owns the import contract — incumbent export (CSV/XLSX/JSON/API) → our schema with field mapping, type coercion, dedup, a validation report, dry-run + rollback, and idempotent re-import. Source playbooks for ServiceTitan, Toast…