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/wednesday-solutions/ai-agent-skillsWrote 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/commands/wednesday-solutions/ai-agent-skills/brownfield-map)<a href="https://agentmods.dev/commands/wednesday-solutions/ai-agent-skills/brownfield-map"><img src="https://agentmods.dev/badge/commands/wednesday-solutions/ai-agent-skills/brownfield-map/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/commands/wednesday-solutions/ai-agent-skills/brownfield-map"><img src="https://agentmods.dev/badge/commands/wednesday-solutions/ai-agent-skills/brownfield-map.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.00000 | $0.01179 |
| Opus 5 | $0.00000 | $0.00589 |
| Sonnet 5 | $0.00000 | $0.00236 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
brownfield-map 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 10d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/brownfield-map — Full Codebase Analysis
Purpose
Run a complete brownfield analysis on the codebase and generate MASTER.md, summaries, risk scores, and all derived analytics.
Trigger
- "Map the entire codebase"
- "Analyze this project"
- "Update codebase intelligence"
Type: /brownfield-map [--full]
Steps
1. Validate environment
Check that the project root contains a recognizable project file:
package.json(Node.js)go.mod(Go)PodfileorPackage.swift(iOS/Swift)setup.pyorpyproject.toml(Python)Gemfile(Ruby)
If none found, stop and suggest the current directory.
2. Check for API key (optional)
If .wednesday/config.json exists and has an OpenRouter API key, the map will use LLM enrichment.
If no key, the map proceeds with deterministic analysis only (no LLM summaries).
Output: "Running full analysis mode" or "API key not configured — skipping LLM enrichment"
3. Execute the map command
wednesday-skills map --full
Wait for completion. The script will:
- Parse all source files
- Build the dependency graph
- Compute risk scores for each file
- Detect daemons and adapters
- Find dead code
- Detect circular dependencies
- Create coverage gaps report
- Generate module summaries (with LLM if API key exists)
- Write
.wednesday/codebase/directory with:MASTER.md(main intelligence document)dep-graph.json(full dependency graph)summaries.json(module summaries)analysis/blast-radius.json(transitive impacts)analysis/safety-scores.json(risk scoring)analysis/dead-code.json(unused files + exports)
4. Parse the output and report
After the command completes, query the DB for final stats:
const queries = require('./.claude/query-helpers.js');
const stats = queries.getCodebaseStats();
const highRiskFiles = queries.getHighRiskFiles(minRisk = 60);
const deadCode = queries.getAllDeadCode();
const circularDeps = queries.getCircularDependencies();
const entryPoints = queries.getEntryPoints();
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.
- 10d ago First seen · 165 lines · 0 tokens per session scan A 7066e319f997
brownfield-map is a command published in the GitHub repository wednesday-solutions/ai-agent-skills (168 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,179 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-30.
Other commands, from other repositories
sdd-apply
Implement SDD tasks — writes code following specs and design.
sdd-explore
Explore and investigate an idea or feature — reads codebase and compares approaches.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
gentle-sdd-ff
Fast-forward all SDD planning phases — proposal through tasks.
ink-art
Hand-drawn ink-on-white doodle animation — a character that draws itself then walks/dances/waves, or a deadpan contraption explainer. Vector, deterministic, rendered via HyperFrames to MP4.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.