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 skills add jeunessegamesee/clew --skill cartograph-use-casegit clone --depth 1 https://github.com/jeunessegamesee/clewWrote 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/skills/jeunessegamesee/clew/cartograph-use-case)<a href="https://agentmods.dev/skills/jeunessegamesee/clew/cartograph-use-case"><img src="https://agentmods.dev/badge/skills/jeunessegamesee/clew/cartograph-use-case/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/skills/jeunessegamesee/clew/cartograph-use-case"><img src="https://agentmods.dev/badge/skills/jeunessegamesee/clew/cartograph-use-case.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.00054 | $0.00429 |
| Opus 5 | $0.00027 | $0.00215 |
| Sonnet 5 | $0.00011 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
cartograph-use-case 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 11d 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
Cartograph a use case
This session is expensive on purpose. Write the map, then stop. Do not also implement the feature.
Read tree.md, communication-types.md, dispatch.md.
Write a tree per use case: Input → Branches → Output. This service owns one level; next points at another service’s tree (same monorepo or another repo).
If maps already exist, prefer the research-use-case skill (gap-fill). Use this skill for a first tree or a full remap of one service — not the whole monorepo in one session. After writing hops.md, run clew score --root <repo> and confirm the new tree removed a P0.
- Forest first: each inbound event/request → which tree? Event name and/or
kind/typemay be a use case. - For each tree, one Input node (interaction, transport, contract, example, stitch).
- Under that input, Branches (
when/also/else) on payload fields. Each taken path ends in one or more Output nodes (interaction, transport, contract, example,nextor terminal). - Nested decisions after an output belong in the downstream tree, not here.
- Request-response: trace ok. Command/event/webhook: stitch + logs. One real payload per path (leaf), not one happy path.
elseis required. Unknown values are a trap.- Commit hops + examples. Stop.
Do not paste another service’s schema. Point at their hops file.
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.
- 11d ago First seen · 25 lines · 0 tokens per session scan A 6cb9c0d0f2f3
cartograph-use-case is a skill published in the GitHub repository jeunessegamesee/clew (0 stars, last pushed 16d ago), licensed MIT. It adds 54 tokens to every session and 429 once invoked, about $0.0003 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.
Other skills, from other repositories
go
Use when writing, reviewing, testing, or shipping Go code and HTTP services: idioms, %w error wrapping, goroutine/context/errgroup concurrency, net/http 1.22 routing, log/slog, project layout, table-driven tests, Go hardening. NOT language-agnostic threat modeling (that is secure-coding), NOT Dockerfile/CI shipping…
rust-conventions
Rust code conventions covering edition 2024, cargo fmt/clippy, Result-based error handling, unsafe discipline, async with tokio, API-guideline naming, trait implementations, benchmarking, and security scanning. Load when writing or reviewing Rust code.
bindings
Cross-language binding architecture rules: bindings as minimal glue, canonical API surface ordering (core, ABI, language), per-language test suites in CI, generated-code discipline, and error/async boundary preservation. Load when designing or reviewing polyglot language bindings for a shared core.
go-swagger3-docs
Documents existing Go HTTP APIs with go-swagger3 godoc @ annotations and struct tags, then generates OpenAPI 3 specs. Use when the user asks to document an API, add Swagger/OpenAPI comments, generate oas.json/yml, or mentions go-swagger3.
go-docs
Go 1.26 — language specification, standard library, concurrency, modules, tools, testing, crypto, networking, database access, and idiomatic patterns.
golang-samber-do
Dependency injection in Golang using samber/do — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Apply when using or adopting samber/do, when the codebase imports github.com/samber/do or github.com/samber/do/v2, or when refactoring manual constructor…