Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Zyrexnn/Cybermesnpx agentmods add commands/zyrexnn/cybermes/surfaceWrote 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/zyrexnn/cybermes/surface)<a href="https://agentmods.dev/commands/zyrexnn/cybermes/surface"><img src="https://agentmods.dev/badge/commands/zyrexnn/cybermes/surface/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/zyrexnn/cybermes/surface"><img src="https://agentmods.dev/badge/commands/zyrexnn/cybermes/surface.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.00458 |
| Opus 5.5 | $0.00000 | $0.00183 |
| Sonnet 5.5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
surface 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.
This is a copy
100% identical to surface — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
name: surface
description: Show ranked attack surface for a target from its recon manifest + hunt memory. Deterministic backing is cbh surface <target> (reads recon//manifest.json); LLM layer adds ledger signal. Usage: /surface target.com
/surface
View the prioritized attack surface for a target.
What This Does
- Reads the recon manifest at
recon/<target>/manifest.json(produced bycbh recon) — the deterministic ranking comes fromcbh surface <target> - Reads hunt memory for patterns and previously tested endpoints
- Layers
engine/skill_map.py(surface → bug-class → skill) + ledger signal on top of the manifest'sranked_surface(P1/P2/Kill) - Outputs P1 (start here), P2 (after P1), and Kill List (skip)
The manifest is the recon→hunt contract — see
docs/recon-manifest.md. Runcbh surface <target>for the raw deterministic ranking.
Usage
/surface target.com
Prerequisites
Run /recon target.com first. If no recon data exists, you'll be prompted to run recon.
Output
ATTACK SURFACE: target.com
═══════════════════════════════════════
Priority 1 (start here):
1. api.target.com/v2/users/{id} — IDOR candidate
Tech: Express + PostgreSQL | First seen 12 days ago
Suggested: numeric ID swap on GET/PUT/DELETE
2. api.target.com/graphql — introspection enabled, 47 mutations
Suggested: field-level auth check on sensitive mutations
Priority 2 (after P1):
1. cdn.target.com:8443/upload — file upload endpoint
Suggested: extension bypass, magic bytes
Kill List (skip):
- static.target.com — CDN only
- docs.target.com — third-party hosted
Memory:
- Pattern from alpha.com (same tech): auth bypass via method override ($800)
- 3 endpoints tested in previous session, 5 remain
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 · 58 lines · 0 tokens per session scan A b0af55c13783
surface is a command published in the GitHub repository Zyrexnn/Cybermes (668 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 458 tokens. A static security scan graded it A with 0 findings. It is 100% identical to surface, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
sicario.assess
Assess the repository against SicarioSpec guardrails.
sicario.review
Review the active spec, plan, tasks, staged changes, or branch for security and governance gaps.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.