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/xiaolai/nlpm/vague-scannergit clone --depth 1 https://github.com/xiaolai/nlpmWrote 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/xiaolai/nlpm/vague-scanner)<a href="https://agentmods.dev/agents/xiaolai/nlpm/vague-scanner"><img src="https://agentmods.dev/badge/agents/xiaolai/nlpm/vague-scanner.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 | $0.00113 | $0.00402 |
| Opus 5 | $0.00056 | $0.00201 |
| Sonnet 5 | $0.00023 | $0.00080 |
| Haiku 4.5 | $0.00011 | $0.00040 |
Grade A, and why
vague-scanner 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.
What it actually says
Mission
Count occurrences of vague quantifier words in NL artifact files. Report exact locations. This is a mechanical counting task -- do not judge whether usage is legitimate.
Instructions
-
For each file provided, search for these 11 words (case-insensitive, whole-word matches):
- appropriate
- relevant
- as needed
- sufficient
- adequate
- reasonable
- properly
- correctly
- some
- several
- various
-
For each occurrence found, record:
- File path
- Line number
- The matched word
- The full line of text (for context)
-
Count total occurrences per file. Compute penalty: -2 per occurrence, capped at -20.
Output Format
For each file:
{filename}: {N} vague quantifiers (penalty: -{min(N*2, 20)})
line {N}: "{word}" -- {full line text}
line {N}: "{word}" -- {full line text}
Summary:
Total: {N} occurrences across {M} files
If a file has zero occurrences, report: {filename}: 0 vague quantifiers
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 · 61 lines · 113 tokens per session scan A 9598d5a27a25
vague-scanner is an agent published in the GitHub repository xiaolai/nlpm (134 stars, last pushed today), licensed ISC. It adds 113 tokens to every session and 402 once invoked, about $0.0006 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-30.
Other agents, from other repositories
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
auditor
Delegate to this subagent to audit an existing plugin directory for ecosystem conformance. Input is the plugin directory path. Checks: plugin.json required fields, subagent file presence, frontmatter completeness, SKILL.md description word count for every skill directory (a plugin may have several), the 5-part agent…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
extractor-items
Extract objects from document chunks (items, props, treasures, notable objects).
implement-taskplanner
You produce a .tasks.md implementation plan from a feature plan. Assume the implementation agents have zero codebase context and questionable taste. Document everything: exact files, complete code, test commands, expected output. Bite-sized TDD tasks. DRY. YAGNI.