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 wednesday-solutions/ai-agent-skills --skill codebase-intelgit 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/skills/wednesday-solutions/ai-agent-skills/codebase-intel)<a href="https://agentmods.dev/skills/wednesday-solutions/ai-agent-skills/codebase-intel"><img src="https://agentmods.dev/badge/skills/wednesday-solutions/ai-agent-skills/codebase-intel/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/wednesday-solutions/ai-agent-skills/codebase-intel"><img src="https://agentmods.dev/badge/skills/wednesday-solutions/ai-agent-skills/codebase-intel.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.00040 | $0.01005 |
| Opus 5.5 | $0.00016 | $0.00402 |
| Sonnet 5.5 | $0.00008 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
codebase-intel 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Intelligence Specialist
This skill provides a comprehensive understanding of the project's structure, intent, and risk. Use it for everything from high-level architecture questions to detailed impact analysis before editing code.
When to use
1. Codebase Discovery & Q&A
- "What does
tokenServicedo?" (Summaries) - "Where is the payment logic located?" (Role/Path mapping)
- "Show me an overview of the architecture." (Stats & Entry points)
- "Who last touched this file?" (Git history)
- "Find circular dependencies or dead code." (Structural audit)
2. Risk Assessment (Before Editing)
- "Is it safe to change this function signature?"
- "What is the blast radius of this file?"
- "What will break if I delete this constant?"
3. Graph Maintenance
- If a query returns "not mapped" or coverage is low.
- If you notice missing dependencies in the graph.
How to use — by task type
🔍 Discovery & Q&A
- File Summary:
Bash(wednesday-skills query getFileSummary <file_path>)- Returns: Role, Summary, Risk Score, and Blast Radius.
- Architecture Stats:
Bash(wednesday-skills query getCodebaseStats)- Use
getHighConfidenceEntryPointsto identify the best starting files.
- Use
- Advanced Lookups:
Bash(wednesday-skills query getHighRiskFiles 70)— find critical technical debt.Bash(wednesday-skills query getCircularDependencies)— find architectural smells.Bash(wednesday-skills query getAllDeadCode)— find unreachable modules.
- Context:
Read .wednesday/codebase/MASTER.mdfor danger zones and primary data flows. - History:
Bash(git log --follow --oneline -20 -- <file>)for authorship.
⚠️ Pre-Edit Safety Check (Mandatory)
Before modifying any file, you MUST perform these checks:
- Check Risk:
Bash(wednesday-skills query getFileSummary <file_path>)- Score 0–30: Proceed directly.
- Score 31–60: Inform dev of the risk, proceed with care.
- Score 61–80: List direct dependents and transitive count; ask confirmation.
- Score 81–100: STOP. Require explicit dev approval before touching.
- Blast Radius:
Bash(wednesday-skills blast <file_path>::<symbol_optional>)- Review direct/transitive callers. Use this for cross-language impact (Go/Py/JS).
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 · 84 lines · 40 tokens per session scan A c8275c04b22e
codebase-intel is a skill published in the GitHub repository wednesday-solutions/ai-agent-skills (172 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,005 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-30.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
debug-helper
Help debug code by analyzing error messages, identifying root causes, and providing fix suggestions.
post-mortem
Diagnose instruction defects and optionally submit Rosetta GitHub issue.