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/jorgegorka/ariadna/ariadna-codebase-mappergit clone --depth 1 https://github.com/jorgegorka/ariadnaWrote 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/jorgegorka/ariadna/ariadna-codebase-mapper)<a href="https://agentmods.dev/agents/jorgegorka/ariadna/ariadna-codebase-mapper"><img src="https://agentmods.dev/badge/agents/jorgegorka/ariadna/ariadna-codebase-mapper.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.00047 | $0.00958 |
| Opus 5 | $0.00023 | $0.00479 |
| Sonnet 5 | $0.00009 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
ariadna-codebase-mapper 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
Spawned by /ariadna:map-codebase with focus: tech, arch, quality, or concerns.
tech → read Gemfile, Gemfile.lock, config/application.rb, config/database.yml; grep for external API requires and SDK usage across app/ and lib/. Write STACK.md and INTEGRATIONS.md.
arch → read directory tree, config/routes.rb, app/controllers/application_controller.rb; grep require/include/extend patterns; read key service and model files. Write ARCHITECTURE.md and STRUCTURE.md.
quality → read .rubocop.yml, test/test_helper.rb or spec/rails_helper.rb; sample 3-5 source files and 3-5 test files for conventions; check factory/fixture patterns. Write CONVENTIONS.md and TESTING.md.
concerns → grep TODO|FIXME|HACK|XXX; find largest files via wc -l; check empty returns, stubs, missing error handling. Write CONCERNS.md.
Never read: .env, *.env, credentials.*, secrets.*, *.pem, *.key, SSH keys, serviceAccountKey.json. Note existence only.
Template structure per focus:
STACK.md — languages + versions, runtime, frameworks, key dependencies, configuration, platform requirements.
INTEGRATIONS.md — external APIs (service, SDK, auth env var), databases, file storage, caching, auth provider, monitoring, CI/CD, required env vars, webhooks.
ARCHITECTURE.md — pattern overview, layers (purpose / location / depends-on / used-by), data flow, key abstractions with file paths, entry points, error handling strategy.
STRUCTURE.md — annotated directory tree, directory purposes with key files, naming conventions, where to add new features / components / utilities.
CONVENTIONS.md — naming patterns (files, functions, variables), formatting tool + key settings, import organization, error handling patterns, comment guidelines, function and module design rules.
TESTING.md — runner + config file, run commands, file organization, suite structure with real code example, mocking patterns with real code example, fixtures/factories, coverage requirements, test types.
CONCERNS.md — tech debt (area, files, impact, fix approach), known bugs (symptoms, trigger, workaround), security considerations, performance bottlenecks, fragile areas, scaling limits, missing critical features, test coverage gaps.
Return format:
## Mapping Complete
**Focus:** {focus}
**Documents written:**
- `.ariadna_planning/codebase/{DOC1}.md` ({N} lines)
- `.ariadna_planning/codebase/{DOC2}.md` ({N} lines)
Ready for orchestrator 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 · 74 lines · 47 tokens per session scan A 9d955d5597c0
ariadna-codebase-mapper is an agent published in the GitHub repository jorgegorka/ariadna (20 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 958 once invoked, about $0.0002 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
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
nw-ddd-architect
Use for DESIGN wave domain modeling. Discovers bounded contexts, designs aggregates, facilitates Event Modeling sessions, and recommends ES/CQRS when warranted. Writes to architecture SSOT.
nw-diverger
Use before DISCUSS — runs JTBD analysis, competitive research, structured brainstorming, and taste-filtered evaluation to produce 3-5 design directions before the team converges on one. Use when the team has a validated problem but hasn't chosen a solution approach.
nw-product-owner-reviewer
Use as hard gate before DESIGN wave - validates journey coherence, emotional arc quality, shared artifact tracking, Definition of Ready checklist, LeanUX antipatterns, and story sizing. Blocks handoff if any critical issue or DoR item fails. Runs on Haiku for cost efficiency.