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 coroboros/agent-skills --skill apexgit clone --depth 1 https://github.com/coroboros/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/coroboros/agent-skills/apex)<a href="https://agentmods.dev/skills/coroboros/agent-skills/apex"><img src="https://agentmods.dev/badge/skills/coroboros/agent-skills/apex/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/coroboros/agent-skills/apex"><img src="https://agentmods.dev/badge/skills/coroboros/agent-skills/apex.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.00046 | $0.03815 |
| Opus 5 | $0.00023 | $0.01907 |
| Sonnet 5 | $0.00009 | $0.00763 |
| Haiku 4.5 | $0.00005 | $0.00381 |
Grade A, and why
apex 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 yesterday.
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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apex
Critical — Adversarial verification
Verify consequential findings and decisions before acting on them.
- Seek counterexamples and independent evidence for load-bearing or contested claims. Use fresh reviewers when available and useful; label sequential self-review as less independent.
- Resolve material findings by correction, evidence-backed refutation, or an explicit remaining risk. Never silently drop them.
- Evidence decides, not reviewer counts or confidence alone. One reproducible defect can invalidate a conclusion.
- Scale verification to the stakes. Keep settled facts settled and reversible, low-impact checks light.
Important — Engineering discipline
Apply these rules when writing, editing, or proposing code.
- Solve the accepted problem with the smallest complete change. Reuse existing mechanisms; preserve unrelated work. Validate external inputs and real failure states.
- Read the affected implementation, callers, and shared utilities before editing. Ground code claims in inspected evidence.
- Implement the general behavior. Tests must distinguish correct behavior from the defect; never hard-code to fixtures or preserve a demonstrably wrong test.
- Carry scope, corrections, and existing authorization through handoffs. Run applicable required checks; repeat them only for changed behavior or unresolved failures.
Critical — Label hygiene
Remove private planning labels and process narration from shipped code and prose. State the domain behavior directly.
- Planning labels — replace
WS-N,Phase-A,Step-3, and private plan names with domain terms. - Process narration — remove authoring history and references that require private planning context. Explain the resulting behavior or constraint.
What ships with it
21 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 2.7 KB
- references/derivation-lens.md 2.4 KB
- scripts/resume_lookup.sh 2.0 KB runs code
- scripts/setup-templates.sh 5.0 KB runs code
- scripts/update-progress.sh 2.2 KB runs code
- scripts/validate_state.sh 2.3 KB runs code
- steps/step-00-init.md 9.9 KB
- steps/step-00b-branch.md 3.2 KB
- steps/step-00b-economy.md 4.8 KB
- steps/step-00b-interactive.md 3.5 KB
- steps/step-01-analyze.md 15 KB
- steps/step-02-plan.md 9.3 KB
- steps/step-03-execute.md 7.6 KB
- steps/step-04-examine.md 10 KB
- templates/00-context.md 732 B
- templates/01-analyze.md 571 B
- templates/02-plan.md 476 B
- templates/03-execute.md 169 B
- templates/04-examine.md 518 B
- templates/README.md 3.8 KB
- templates/step-complete.md 101 B
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.
- yesterday Changed · -2 lines 2cebbec698b4
- 9d ago First seen · 270 lines · 46 tokens per session scan A 47a7ef890b67
apex is a skill published in the GitHub repository coroboros/agent-skills (4 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 3,815 once invoked, about $0.0002 per session on Opus 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
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.
agent-qa-testing
Agent davranis testi ve protokol uyumluluk dogrulamasi. Agent'larin tanimli rollerine uygun davranip davranmadigini assertion-based test'lerle olcer. Personality drift, role violation ve output kalite regresyonu tespit eder.
aws-patterns
Lambda best practices, S3 event patterns, SQS/SNS fanout, and DynamoDB access patterns for serverless AWS architectures.
review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…