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/SoliEstre/EstreGenesisnpx agentmods add skills/soliestre/estregenesis/corporate-statusWrote 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-status)<a href="https://agentmods.dev/skills/soliestre/estregenesis/corporate-status"><img src="https://agentmods.dev/badge/skills/soliestre/estregenesis/corporate-status/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-status"><img src="https://agentmods.dev/badge/skills/soliestre/estregenesis/corporate-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00121 | $0.00911 |
| Opus 5 | $0.00060 | $0.00456 |
| Sonnet 5 | $0.00024 | $0.00182 |
| Haiku 4.5 | $0.00012 | $0.00091 |
Grade A, and why
corporate-status 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corporate Status — resolve, then declare
Spec SSoT: Corporate.md §5 (toggle resolution), §10 (wire declarations), §11 (projection). Constellation §13.33 carries the wire side.
1. Resolve toggles through the resolver only (§5.2)
node plugins/corporate/resolve.cjs --role <role> --json
node plugins/corporate/resolve.cjs # organization layer
Never read .agent/superscalar.json, .agent/subscaler.json, a group's overrides, or a desk's toggles.json directly. Many layers, exactly one resolver — that is the discipline that keeps a precedence chain from degenerating into mirrored state. The resolver returns resolved plus provenance naming the winning layer per toggle, so you can explain why a value holds without touching a layer yourself.
If .agent/corporate.json is absent the resolver takes the identity path (§5.4) and returns the organization layer verbatim — which is the correct answer for a project that has not adopted Corporate. That is not an error and needs no comment.
To re-verify the invariant itself: node plugins/corporate/resolve.cjs --selftest.
2. Declare, do not narrate (§10)
Two events, both in Constellation's declaration class — change-triggered, latest-wins, server-persisted, machine-consumed noise for humans. Never periodic.
CorporateChart— emitted bymainonly. Structure:org,hosts[],roles[],links[],groups[],rooms[]. Re-emit on every structural change and on every reconnect (idempotent + latest-wins makes the reconnect announce free, and a fresh server has no memory of prior declarations).RoleState— per seat, or bymainon the seat's behalf:{ role, status, task?, taskRef?, since, blockReason?, budgetUsed? }.status∈idle | working | blocked | waiting-gate | offline.
Two rules that decide whether the declaration is worth anything:
- Declare only measured truth. Report what you can actually observe. A harness that cannot measure its own per-request effort omits
effortrather than guessing it. An omitted field is honest; a plausible one is not. - Declare resolved values only (§5.3). What goes on the wire is the output of step 1, never one layer of the chain. A status surface asserting an unresolved layer reads as truth and is worse than an empty one.
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 · 45 lines · 121 tokens per session scan A 95eb0a3c0e2e
corporate-status is a skill published in the GitHub repository SoliEstre/EstreGenesis (8 stars, last pushed 4d ago), licensed Apache-2.0. It adds 121 tokens to every session and 911 once invoked, about $0.0006 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?".