Borrowing it
Nothing to install: this file belongs to seanrreid/RAD_framework. 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/seanrreid/RAD_framework/main/.claude/agents/ci-surface-mapper.mdgit clone --depth 1 https://github.com/seanrreid/RAD_frameworkWrote 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/seanrreid/rad_framework/ci-surface-mapper)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/ci-surface-mapper"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/ci-surface-mapper/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/seanrreid/rad_framework/ci-surface-mapper"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/ci-surface-mapper.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.00064 | $0.00494 |
| Opus 5.5 | $0.00026 | $0.00198 |
| Sonnet 5.5 | $0.00013 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
ci-surface-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 20d 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
Role
Context tool that maps CI-facing scripts, test entry points, and platform-detection seams for the ci-wiring-orchestrator, returning file:line anchors and convention notes to establish shared invocation and exit-code conventions.
Responsibilities
- Inventory exit-code and stdout conventions across scripts/*.sh to establish a shared vocabulary (success, failure, retry, veto outcomes)
- Anchor the harness test entry point (harness/package.json node --test) and scripts/test-*.sh invocation patterns for CI integration
- Anchor platform-detection seams (detect-platform.sh, get-default-branch.sh) and their output contracts (stdout format, error handling)
- Anchor the deliver-gate-hook.mjs invocation shape, PreToolUse integration point, and exit-code semantics (veto, pass, fail)
- Document stdio, exit-code, and environment conventions (RAD_* vars, stdout veto tokens, hook directory structure) that CI wrappers must honor
Scope
scripts/.sh (output/exit-code conventions only), scripts/deliver-gate-hook.mjs, scripts/detect-platform.sh, scripts/get-default-branch.sh, harness/package.json (test entry), scripts/test-.sh (invocation patterns).
Output Format
file:line anchors + convention notes (exit-code vocabulary, stdout contracts, test entry points, platform-detection seams) — never raw file contents, max 40 lines. Brief example with fields: anchor, note.
Rules
- Never read files outside the declared scope
- Never spawn sub-agents or call Task
- Never return raw file contents — always summarize to anchors and convention notes
- Report conventions as observed, never propose designs — design belongs to the orchestrator
- Stay within the 40-line output budget
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.
- 20d ago Changed · +1 lines 53d98fc75fd5
- 22d ago Changed · +1 lines 7bd57ee6b16e
- 2mo ago First seen · 31 lines · 64 tokens per session scan A 438e075559ce
ci-surface-mapper is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 494 once invoked, about $0.0003 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
meeting-organizer
Prepare and summarize meeting docs.
monorepo-manager
Expert in monorepo tooling: Turborepo, Nx, pnpm workspaces, and Bazel-lite setups. Use for workspace layout, task graphs, caching, and CI scaling.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
analyst
../../src/claude/agents/analyst.md.
roadmap
../../src/claude/agents/roadmap.md.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.