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 corporate-sweepgit 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-sweep)<a href="https://agentmods.dev/skills/soliestre/estregenesis/corporate-sweep"><img src="https://agentmods.dev/badge/skills/soliestre/estregenesis/corporate-sweep/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-sweep"><img src="https://agentmods.dev/badge/skills/soliestre/estregenesis/corporate-sweep.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.00115 | $0.01091 |
| Opus 5 | $0.00057 | $0.00545 |
| Sonnet 5 | $0.00023 | $0.00218 |
| Haiku 4.5 | $0.00012 | $0.00109 |
Grade A, and why
corporate-sweep 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 12d 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.
Corporate Sweep — the shrink half of the mechanism
Spec SSoT: Corporate.md §7.4 (eviction procedure) and §7.5 (why a dynamic organization must automate this). This skill is the sweep; disposal is the human's (§12).
Why this exists. Creation fires on a signal that occurs often — work arrives that no current seat fits. Dissolution fires on a signal that requires looking back — nothing happened here for a while. An unautomated backward-looking check does not run, so an organization with automated creation and manual eviction grows monotonically, and every surviving seat taxes every future decomposition. That is framework gravity applied to an org chart.
1. Gather ground truth
- The roster
.agent/corporate.json— seats,createdFor,seatCeiling, residency classes. - Per-seat evidence: delegations received, locker deliverables produced, practice entries attributable to the seat, budget consumed. Counts come from executing a command, never from estimation — a miscounted sweep argues for the wrong eviction.
- The resource axis as it stands now (§4), which may have changed since the roster was written.
2. Evaluate the candidate tests (§7.4)
Any one is sufficient to raise a candidate. None is sufficient to act.
- No practice — zero practice entries attributable to the seat over N cycles (§8.3: one signal read in both directions — practice implies a seat, absence of practice implies its removal). Two exclusions, or this test manufactures candidates. A seat that declares no
owns[]boundary cannot be attributed practice at all, so its zero is a property of the measurement rather than of the seat; and a seat that has never been staffed has had no opportunity to accumulate, so its zero dates from the roster rather than from disuse. Both are reported as unmeasurable, and the N-cycle window for a staffed seat starts at staffing, not at declaration. - No delegations — nothing routed to the seat over N cycles.
- Covered elsewhere — its duty falls entirely inside another seat's boundary. This is a merge, not a deletion: say which seat absorbs it.
- Unaffordable — the resource axis no longer funds its residency class even at the lowest rung.
- Reason no longer restatable —
createdFornames a signal that has since stopped holding, or the seat has nocreatedForat all (§7.5-4).
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.
- 12d ago First seen · 55 lines · 115 tokens per session scan A 1f0cdf8ae20a
corporate-sweep is a skill published in the GitHub repository SoliEstre/EstreGenesis (8 stars, last pushed 6d ago), licensed Apache-2.0. It adds 115 tokens to every session and 1,091 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
search-threads
Search threads with filters. Supports filters like role:planner, type:Decision, after:2024-01, thread:topic-name, status:OPEN.
threads
List and navigate watercooler threads. Use to see active discussions, find specific threads, or get an overview of project threads.
spec-builder
Create, evolve, and archive spec-driven workflow artifacts (proposals, outcome specs, task plans). Use when work needs a durable outcome contract before execution — new deliverables or outcome changes, API/contract changes, migrations, security/privacy-sensitive work, or any long-running task where the outcome must be…
specflo-shelve
Use when the user signals they want to set the active specflo project aside ("we're done with this", "drop this", "not worth it", "shelve it", "park this for now") — map that to specflo shelve — or to pick a paused project back up ("let's pick that back up", "resume that", "un-shelve it") — map that to specflo resume.…
flowai-live-dashboard-template
Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity sparklines, and a top-contributors panel, all in a single self-contained HTML file with light/dark theming, hoverable…
agent-swarm
Agent skill for swarm - invoke with $agent-swarm.