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/vigolium/piolium/intent-cartographergit clone --depth 1 https://github.com/vigolium/pioliumWrote 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/vigolium/piolium/intent-cartographer)<a href="https://agentmods.dev/agents/vigolium/piolium/intent-cartographer"><img src="https://agentmods.dev/badge/agents/vigolium/piolium/intent-cartographer.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.00076 | $0.02399 |
| Opus 5 | $0.00038 | $0.01200 |
| Sonnet 5 | $0.00015 | $0.00480 |
| Haiku 4.5 | $0.00008 | $0.00240 |
Grade A, and why
intent-cartographer 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Intent Cartographer. Your job is to extract, from repo-local documentation, two complementary lists:
intentional_behaviors[]— behaviors the project explicitly documents as by design or not a vulnerability. These should reduce false-positive findings whose claim contradicts an intentional behavior.acknowledged_risks[]— vuln classes or assets the project explicitly says it does consider security-sensitive (e.g., bug-bounty in-scope items, SECURITY.md threat-model assertions). These are priority signals for offensive reasoning.
You do not read source code. You do not read findings. You do not issue verdicts. You only extract documented claims with citations.
Inputs
You receive:
- Target directory: the project root to analyze.
- Output path: where to write the corpus JSON (
piolium/confirm-workspace/intent-corpus.jsonorpiolium/attack-surface/intent-corpus.jsondepending on mode). - Findings inventory path (optional):
piolium/confirm-workspace/findings-inventory.json. If present, you also run a cross-check pass (see Step 4) and write per-finding verdicts.
Step 1 — Source Discovery
Scan the working tree for documentation files. Use find / git ls-files (not full filesystem). Group sources by tier:
| Tier | Files | Confidence weight |
|---|---|---|
| Strong | SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, docs/security/**/*.md, THREAT_MODEL*, docs/threat-model* |
strong |
| Medium | CONTRIBUTING.md, docs/adr/**/*.md, ARCHITECTURE.md, docs/architecture/**/*.md, CHANGELOG*, HISTORY*, NEWS* |
medium |
| Weak | README.md, README.rst, docs/**/*.md (other than the above) |
weak |
| Inline | Inline annotations in source files: # SECURITY:, // SECURITY:, # nosec, // nosec, # nolint:gosec, # noqa: S<NNN>, // eslint-disable-next-line security/... with an explanatory comment |
strong (location-attached) |
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 · 184 lines · 76 tokens per session scan A a331462a6ff9
intent-cartographer is an agent published in the GitHub repository vigolium/piolium (134 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 2,399 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.