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 SoliEstre/EstreGenesis --skill corporategit clone --depth 1 https://github.com/SoliEstre/EstreGenesisWrote 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/soliestre/estregenesis/corporate)<a href="https://agentmods.dev/skills/soliestre/estregenesis/corporate"><img src="https://agentmods.dev/badge/skills/soliestre/estregenesis/corporate/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/soliestre/estregenesis/corporate"><img src="https://agentmods.dev/badge/skills/soliestre/estregenesis/corporate.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.00162 | $0.02745 |
| Opus 5 | $0.00081 | $0.01373 |
| Sonnet 5 | $0.00032 | $0.00549 |
| Haiku 4.5 | $0.00016 | $0.00275 |
Grade A, and why
corporate 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 10d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corporate — stand up a durable-role organization
Spec SSoT: Corporate.md. Read it before acting; this skill is the procedure, not the contract. Where the two disagree the spec wins.
Before anything else, run the rejection rubric (§15). Two checks, in this order, and declining is a normal, correct output of this skill — not a failure to be worked around.
Adoption thresholds — all three must hold: two or three duties genuinely recur across sessions (evidenced, not intuited); the declared resources can fund the proposed seats at their cheapest residency; the coordination need outlives a session.
Rejection conditions (§15.1) — any one firing means do not stand up an organization: high dependency density (units of work editing interdependent parts of one codebase — the single worst-fitting case, route to one seat with context compression instead) · latency is the binding constraint on interactive work · coordination overhead exceeds the parallel gain at this scale · the available model tier is below the autonomy threshold for the duty.
If any check fails, say so plainly, name which one, and recommend the cheaper shape — a Superscalar fan-out plus a board, or a single seat. Standing up an organization the resources cannot run, or that has nothing recurring to do, is the failure this step prevents.
1. Collect the form (§4) — four axes, with costs
Ask about each; present options with their consequences rather than as a menu of words. Record the answers in the roster, because an undeclared organizational prior silently defaults to whatever was decided last.
- Topology — flat peer / hierarchical / mixed. Note the trade: a supervisor seat is itself a cost, and a flat organization pays coordination cost inside every seat instead.
- Drive — event-driven semi-autonomous / goal-driven autonomous / between. This decides where human gates sit, not how capable the organization is.
- Variability — static / dynamic. If dynamic, §7.5 applies and is not optional: the deployment must have a scheduled eviction sweep, human disposal on the gate surface, a declared seat ceiling, and a per-seat
createdForrecord. Say this at the moment the answer is given, not later. - Resources — subscriptions and their tiers, metered API budget, local models, and hosts. This is a hard constraint on the roster, not a preference.
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.
- 10d ago First seen · 94 lines · 162 tokens per session scan A f0e2f7d80b62
corporate is a skill published in the GitHub repository SoliEstre/EstreGenesis (8 stars, last pushed 3d ago), licensed Apache-2.0. It adds 162 tokens to every session and 2,745 once invoked, about $0.0008 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
update-agent-context
This skill should be used to keep CLAUDE.md, AGENTS.md, and the skill files themselves compact, current, and internally consistent. It runs in three phases: Phase 1 performs a one-time structural refactor of CLAUDE.md using a Karpathy-inspired behavioral scaffold and derives AGENTS.md from it by stripping Claude…
watercooler-onboarding
Bootstrap Watercooler memory for a repository by inspecting local code, docs, CI, git history, and existing Watercooler threads, then writing a small set of durable, provenance-backed seed threads that future agents can query and extend. Use when entering a repo for the first time, seeding a repo with Watercooler…
ppgp
Portable Persistent Goal Protocol for long-running coding-agent work. Use when starting, resuming, handing off, distilling, or closing a substantial software goal across long sessions, context compaction, agent replacement, or other Agent Skills-compatible coding-agent environments.
search-threads
Search threads with filters. Supports filters like role:planner, type:Decision, after:2024-01, thread:topic-name, status:OPEN.
watercooler-health
Check watercooler system health — MCP server, baseline graph (T1), git auth, GitHub rate limit, and daemons. Use when syncs break or anything in the watercooler stack behaves unexpectedly.
recall
Recall project context or answer questions about history and decisions. Use before starting work, when investigating unfamiliar code, or asking "What was decided about X?" / "Why did we choose Y?".