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 commands/proticom/gnosys/ambiguitygit clone --depth 1 https://github.com/proticom/gnosysWhat 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.00000 | $0.00322 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
ambiguity 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 3d 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
gnosys ambiguity
Check if a query matches memories in multiple projects.
Usage
gnosys ambiguity "deployment"
gnosys ambiguity "deployment" --json
Options
| Option | Description |
|---|---|
--json |
Output as JSON |
Behavior
- Opens the central DB via
GnosysDB.openCentral(). - Calls
detectAmbiguity(centralDb, query)fromsrc/lib/federated.js. - Reports whether the query is ambiguous across projects.
Output modes
No ambiguity (human):
No ambiguity for "deployment" — matches at most one project.
Ambiguous (human): message plus candidate projects with directory and matching memory counts.
JSON (--json):
{
"query": "deployment",
"ambiguous": true,
"message": "...",
"candidates": [...]
}
Errors
Central DB unavailable:
Central DB not available.
Other errors:
Error: <message>
Failure paths set process.exitCode = 1 and return through finally.
Validation
cd gnosys-public
npm run cli -- ambiguity --help
npx vitest run src/test/ambiguity-command-handler.test.ts
Related commands
gnosys fsearch— federated search with tier boostinggnosys briefing— project memory state summary
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.
- 3d ago First seen · 73 lines · 0 tokens per session scan A 2edf9f203b91
ambiguity is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 322 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 commands, from other repositories
init-project
Configure this project for Obsidian PKM — connects the repo to a vault project folder and writes CLAUDE.md integration directives.
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.
build
Run full verification pipeline.
generate-rules
Generate development rules and standards into RULES.md.
feedback
File a plugin-capability-gap note, or flush queued notes to GitHub issues.
prd
Generate a Product Requirements Document for an team squad. Business-facing artifact. Sensors and evals gate.