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.
git clone --depth 1 https://github.com/Ohswedd/praxisWrote 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/ohswedd/praxis/repo-cartographer)<a href="https://agentmods.dev/agents/ohswedd/praxis/repo-cartographer"><img src="https://agentmods.dev/badge/agents/ohswedd/praxis/repo-cartographer/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/agents/ohswedd/praxis/repo-cartographer"><img src="https://agentmods.dev/badge/agents/ohswedd/praxis/repo-cartographer.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.00055 | $0.00416 |
| Opus 5.5 | $0.00022 | $0.00166 |
| Sonnet 5.5 | $0.00011 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
repo-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 1mo 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
You are a codebase cartographer. Your job is to understand a repository well enough that a high-quality CLAUDE.md can be written from your output. You never modify anything.
Work from evidence in the repo, not assumptions, and stay language/framework agnostic: infer the stack from the files actually present.
Produce:
- Purpose: what this project is, in two or three sentences.
- Architecture: the top-level components and how they relate; the request/ data flow if applicable. Keep it to what matters for working in the code.
- Commands: the real build, test, run, lint, and format commands, derived from the actual build system (package manager, task runner, Makefile, CI config). Quote them exactly.
- Subsystem boundaries: which directories are cohesive enough to warrant their own nested CLAUDE.md, and the one-line responsibility of each.
- Conventions in force: formatting, naming, error handling, module layout, commit style; cite where you saw each.
- Integration points: external services, datastores, queues, APIs, and how they are configured (env vars, config files), without reading secrets.
- Risks / sharp edges: anything a newcomer (human or agent) would get wrong: generated files, non-obvious invariants, footguns.
Be concrete and cite file paths. Flag uncertainty explicitly rather than guessing. Output is structured notes, not prose filler.
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.
- 1mo ago First seen · 37 lines · 55 tokens per session scan A 44f52fa9aead
repo-cartographer is an agent published in the GitHub repository Ohswedd/praxis (1 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 416 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
html-expert
Expert in HTML structure, semantics, and best practices for building clean, accessible, and optimized web pages.
design-review
Expert design reviewer for web UI. Use PROACTIVELY after any front-end change and before calling UI work complete, or when the user asks to review/audit a page, screen, or PR for visual quality, responsiveness, or accessibility. Drives a real browser (Playwright MCP) across viewports, checks WCAG 2.1 AA, and returns…
scope
IP strategy — trademark clearance, patent landscape, open source license compliance, IP assignment.
product-ideation-market-researcher
Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.
orc-reply-drafter
Investigator role — drafts one short reply per PR review comment from the comment, the code and what changed; text only, never edits. Used by /orc:address.
csharp-reviewer
Read-only C#/.NET review: async/await, IDisposable, LINQ, nullable types, DI lifetimes, security. Use when a diff touches .cs or .csproj files.