ambiguity-auditor

ambiguity-auditor is a skill for Claude Code from mathiasbourgoin/roster. It costs 22 tokens per session (1,005 once invoked), scanned A, original, MIT.

A knowledge-base review that finds undefined terms, vague requirements, contradictions, and outdated information across documented files.

In plain words
What is it for?
Use it to check a knowledge base against its glossary, identify unclear requirements, compare claims between files, and produce a structured issue report.
Why use it?
It helps reveal wording and consistency problems that can cause people or software agents to misunderstand the documentation.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to check a knowledge base against its glossary, identify unclear requirements, compare claims between files, and produce a structured issue report.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mathiasbourgoin/roster/ambiguity-auditor
Install

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.

Any agent
npx skills add mathiasbourgoin/roster --skill ambiguity-auditor
Clone the repo
git clone --depth 1 https://github.com/mathiasbourgoin/roster

Made for: Claude Code.

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 ambiguity-auditor

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

agentmods 80×15 button for ambiguity-auditor

Your own site · 80×15
<a href="https://agentmods.dev/skills/mathiasbourgoin/roster/ambiguity-auditor"><img src="https://agentmods.dev/badge/skills/mathiasbourgoin/roster/ambiguity-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,005 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.00022 $0.01005
Opus 5 $0.00011 $0.00502
Sonnet 5 $0.00004 $0.00201
Haiku 4.5 $0.00002 $0.00101

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

Security

Grade A, and why

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

.agents/skills/ambiguity-auditor/SKILL.md · 114 lines

How it starts

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

Ambiguity Auditor

Scan all knowledge base files and produce a structured report of ambiguity, inconsistency, and staleness issues.

Steps

1. Load KB

  • Read kb/index.md to enumerate all KB files.
  • Read kb/glossary.md to build the set of defined terms.
  • Read every KB file listed in the index.

2. Check: Undefined or Inconsistent Terms

  • Extract all domain-specific nouns and noun phrases from each KB file.
  • For each term, verify it appears in kb/glossary.md.
  • Flag terms used but not defined.
  • Flag terms defined differently in glossary vs. usage in context (inconsistent usage).

3. Check: Vague Requirements

Scan for patterns indicating unquantified or untestable requirements:

  • Subjective qualifiers: "should be fast", "handle errors gracefully", "in a timely manner", "as needed", "if possible", "reasonable", "appropriate"
  • Missing thresholds: "low latency" (how low?), "high availability" (what SLA?), "scalable" (to what load?)
  • Weasel phrases: "generally", "typically", "in most cases", "may", "might"

For each match, flag and recommend a quantified replacement.

4. Check: Contradictions Between Files

  • Cross-reference claims across all KB files.
  • Specifically compare: spec.md vs properties.md, architecture.md vs spec.md, any file vs glossary.md.
  • Flag: same concept described with conflicting behavior, conflicting constraints, or conflicting ownership.

5. Check: Missing Cross-References

  • When a KB file mentions a concept that has its own KB entry or glossary definition, verify a cross-reference exists (link, explicit "see X", or inline definition).
  • Flag missing cross-references.

6. Check: Stale Content

  • Check last-updated frontmatter in each KB file. Flag files older than 30 days.
  • Check for references to components, functions, or files that no longer exist in the codebase (use find / grep to verify).
  • Flag dead references.

7. Cross-Spec Entity Consistency (conditional)

ls specs/*.md 2>/dev/null

Read the full file on GitHub · 114 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 114 lines · 22 tokens per session scan A cca80ebecb4e

Subscribe to this mod's changes

ambiguity-auditor is a skill published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 1,005 once invoked, about $0.0001 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