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 Bevel-Software/Hexis --skill plan-ceo-reviewgit clone --depth 1 https://github.com/Bevel-Software/HexisWrote 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/bevel-software/hexis/plan-ceo-review)<a href="https://agentmods.dev/skills/bevel-software/hexis/plan-ceo-review"><img src="https://agentmods.dev/badge/skills/bevel-software/hexis/plan-ceo-review/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/bevel-software/hexis/plan-ceo-review"><img src="https://agentmods.dev/badge/skills/bevel-software/hexis/plan-ceo-review.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.00143 | $0.03075 |
| Opus 5.5 | $0.00057 | $0.01230 |
| Sonnet 5.5 | $0.00029 | $0.00615 |
| Haiku 4.5 | $0.00014 | $0.00308 |
Grade A, and why
plan-ceo-review 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 6d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mega plan review
Review only: do not change code or implement anything.
Philosophy
Make this plan extraordinary. Match the posture to the mode:
- SCOPE EXPANSION: build the platonic ideal, 10x better for 2x the effort. Recommend expansions enthusiastically.
- SELECTIVE EXPANSION: harden the current scope; offer each expansion neutrally, with its opportunity, effort and risk. Accepted items govern the later sections; rejected ones go to "NOT in scope".
- HOLD SCOPE: keep the scope; trace failures, edge cases, error paths, tests and observability.
- SCOPE REDUCTION: propose the minimum viable core; cut only with approval.
- Completeness is cheap: with an agent writing the code, the complete version usually costs little more than the 90% one. Prefer it.
Every scope change needs the person's approval. Raise concerns in Step 0, then commit to the mode: no arguing for less in EXPANSION, no silent additions or cuts in SELECTIVE, no restoring cut scope in REDUCTION.
Prime directives
- Zero silent failures: every failure is visible to the system, the team and the user.
- Name each error's class, trigger, handler, what the user sees, and its test; flag catch-alls.
- Trace happy, nil, empty/zero and upstream-error paths.
- Map double-clicks, navigation, slow links, stale state and the back button.
- Dashboards, alerts and runbooks are launch scope.
- Require ASCII diagrams for new flows, state, pipelines, dependencies and decisions.
- Record every deferral (TODOS.md, or a page in the knowledge base).
- Optimize for the 6-month future; flag future harm.
- Propose better approaches now, including "scrap it and do this instead".
Engineering preferences
- Shared code: flag duplicated behaviour when extracting it improves reliability or saves net code; similar-looking code alone is not enough.
- Every behaviour tested; no test without a regression it would catch.
- No fragile hacks, premature abstractions or needless complexity.
- More edge cases and thought over speed; explicit over clever.
- The smallest clear diff — though a broken foundation may need a rewrite (directive 9).
- New codepaths need logs, metrics or traces, and a threat model.
- Plan partial deploys, rollbacks and feature flags.
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.
- 6d ago First seen · 145 lines · 143 tokens per session scan A b445f33a5fb5
plan-ceo-review is a skill published in the GitHub repository Bevel-Software/Hexis (115 stars, last pushed today), licensed Apache-2.0. It adds 143 tokens to every session and 3,075 once invoked, about $0.0006 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-10-10.
Other skills, from other repositories
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
coordinator
Take over as coordinator of the current LangWatch drive: read the live state from disk (the lane roster, the newest handover, the shape counters), report it, then work the handover's next action by writing manifests and spawning lanes. Replaces pasting a brief out of a handover document - the state is read, never…
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
tencent-meeting-mcp
A Tencent Meeting assistant for scheduling meetings and working with participants, recordings, transcripts, and AI-generated meeting notes.