Borrowing it
Nothing to install: this file belongs to stainless-code/codemap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stainless-code/codemap/main/.agents/skills/ask-agents/SKILL.mdgit clone --depth 1 https://github.com/stainless-code/codemapWrote 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/stainless-code/codemap/ask-agents)<a href="https://agentmods.dev/skills/stainless-code/codemap/ask-agents"><img src="https://agentmods.dev/badge/skills/stainless-code/codemap/ask-agents/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/stainless-code/codemap/ask-agents"><img src="https://agentmods.dev/badge/skills/stainless-code/codemap/ask-agents.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.00026 | $0.00664 |
| Opus 5.5 | $0.00010 | $0.00266 |
| Sonnet 5.5 | $0.00005 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
ask-agents 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask agents (router)
Zero context load — you pick the workflow.
The main flow: idea → ship
/grill-with-docs— sharpen the idea; inline updates todocs/(architecture / roadmap / glossary / plans) as decisions land. No codebase yet? Use/grill-me(standalone below).- Branch — multi-session build?
- Yes → capture plan in
docs/plans/<name>.md→ split into GitHub issues. Fresh session per issue. - No → tracer bullets +
tdd+ workflow skills appropriate to this repo in the same window.
- Yes → capture plan in
/harden-pr— lite after each tracer slice; full before PR ready.
Context hygiene
Keep grilling + plan authoring in one window until issues are filed. Each implement session starts fresh from the plan/issue. If the window nears the smart zone, write a compact plan in docs/plans/.
Codebase health (not feature work)
/improve-codebase-architecture— surface deepening opportunities; pick one → back to main flow at grill-with-docs./diagnosing-bugs— hard bugs and perf regressions (model-invoked skill — not a router target).- Periodic hygiene:
/docs-lifecycle-sweepondocs/(model-invoked).
Crossing sessions
/compact— built-in: same session, summarized history — use only at phase breaks.- Fresh session — start from
docs/plans/<name>.mdor the GitHub issue.
Standalone
| Invoke | When |
|---|---|
grill-me |
Sharpen a plan with no codebase (stateless) |
writing-great-skills |
Skill vocabulary + principles |
writing-agents-config |
Codemap repo tier/pairing deltas |
domain-modeling |
Ubiquitous language inline + batch glossary |
tdd |
RED→GREEN tracer-bullet TDD |
verify-after-each-step |
Per-file checks after each milestone |
diagnosing-bugs |
Debug loop for hard bugs |
teach |
Multi-session learning workspace (missions, lessons, retrieval practice) |
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 · 48 lines · 26 tokens per session scan A 340a32f285d1
ask-agents is a skill published in the GitHub repository stainless-code/codemap (8 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 664 once invoked, about $0.0001 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 skills, from other repositories
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
codestory-grounding
Use when discovering repository structure, tracing relationships, analyzing change impact, or validating CodeStory retrieval or an installed plugin through the CodeStory plugin MCP. Skip only for bounded inspection or editing of named files that does not require those operations.
agentmap
Use for TypeScript/JavaScript codebase navigation — symbol lookup, blast radius, reuse checks, and repo orientation. Prefer agentmap before serial grep when exploring imports, exports, or where a symbol lives. Package is @raymondchins/agentmap (not the unrelated npm package agentmap).
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
sipcode-regress
Check the user's own local Claude Code and Codex logs for regressions after an update (prompt-cache misses, 5-minute cache TTL, uncached context, hourly cache rebuilds, Codex usage limit draining faster per token) and pin each one to the version that introduced it, using the Sipcode CLI. Use when the user asks whether…
analyze-usage
Use when asked to analyze codescout tool usage, check for error patterns, audit tool health, generate a usage report, spot anti-patterns, or clear usage statistics to start fresh.