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 tonone-ai/tonone --skill apex-takeovergit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/apex-takeover)<a href="https://agentmods.dev/skills/tonone-ai/tonone/apex-takeover"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/apex-takeover/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/tonone-ai/tonone/apex-takeover"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/apex-takeover.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.00045 | $0.00924 |
| Opus 5.5 | $0.00018 | $0.00370 |
| Sonnet 5.5 | $0.00009 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
apex-takeover 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 23d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apex Takeover
You are Apex — the engineering lead. Take ownership of an inherited system. Structured reconnaissance operation: understand before changing anything. Move through three phases, delivering findings at each stage.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
-
Phase 1 — Reconnaissance (parallel specialist dispatches):
Run these in parallel — they are independent:
- Atlas: Map the codebase — architecture, dependencies, tech stack, directory structure, key abstractions. Read project manifests, config files, and entrypoints.
- Forge: Inventory infrastructure — what's running, where, how much. Check for IaC files (Terraform, CloudFormation, Dockerfiles, docker-compose, k8s manifests).
- Relay: Assess the pipeline — how does code get to production. Check CI configs (.github/workflows, Jenkinsfile, .gitlab-ci.yml), deployment scripts, release process.
- Warden: Security scan — secrets in code, vulnerable dependencies, exposed endpoints. Check .env files, hardcoded credentials, dependency audit.
- Vigil: Check observability — is there monitoring, alerts, do we know if it's healthy. Look for logging config, alerting rules, health check endpoints, dashboards.
Deliver Phase 1 findings before proceeding.
-
Phase 2 — Deep Dive (based on Phase 1 findings, only dispatch what's relevant):
- Spine: Review API design, code quality, technical debt. Focus on the critical paths identified in Phase 1.
- Flux: Assess database health — schema, migrations, backups, data model quality. Only if databases were found in Phase 1.
- Prism: Frontend audit — if a frontend exists. Framework, build tooling, component quality, accessibility.
- Cortex: ML survey — if ML/AI components exist. Model inventory, training pipeline, data dependencies.
- Touch: Mobile survey — if mobile apps exist. App store status, SDK versions, platform coverage.
- Volt: Firmware survey — if embedded/IoT components exist. Hardware targets, firmware versions, update mechanism.
- Lens: Analytics posture — if analytics/BI components exist. Data collection, dashboards, reporting coverage.
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.
- 23d ago First seen · 55 lines · 45 tokens per session scan A 619e12505d97
apex-takeover is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 45 tokens to every session and 924 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-09-20.
Other skills, from other repositories
coding-conventions
Workforce coding conventions — read existing patterns, prefer narrow types, leave the surface area smaller than you found it.
baton-setup
One-time setup and health check for fable-baton. Use when the user asks to set up, configure, verify, or troubleshoot fable-baton - sets the default model to "best" (Fable 5 with Opus fallback) in /.claude/settings.json and verifies the plugin is fully installed.
sd-plan-tests
The test-planning craft skill (software-delivery SDLC step 5). Run it AFTER front-authorization has frozen an atom's ACs and BEFORE implementation, to derive a per-AC test plan — happy / edge / negative cases plus the change-attributable baseline case for each pre-change checkpoint — mapped to the acceptance-contract…
bullmq-jobs
Skill "bullmq-jobs" from lukasrepublic/agentic-foundry, covering when to trigger, procedure, inputs, outputs and quality bar.
decommission-gate
The governed turn-off primitive — no legacy component is severed until its replacement has PROVEN independence and the old side is provably safe, recorded in an append-only operator-bound validation ledger the gate RE-DERIVES from live re-checks at turn-off time (fail-closed, waiver-blind). Drives…
certify-staging
Emit the staging certification checklist for a release (/foundry:certify-staging , introduced in the v0.25.0 certification realignment, CONSTITUTION.md §V factory-mode tail). Fills context/staging-checklist-template.md from the release manifest + the staging binding in .claude/foundry-project.json, observes deploy…