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 cdeust/zetetic-team-subagents --skill normative-designgit clone --depth 1 https://github.com/cdeust/zetetic-team-subagentsWrote 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/cdeust/zetetic-team-subagents/normative-design)<a href="https://agentmods.dev/skills/cdeust/zetetic-team-subagents/normative-design"><img src="https://agentmods.dev/badge/skills/cdeust/zetetic-team-subagents/normative-design/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/cdeust/zetetic-team-subagents/normative-design"><img src="https://agentmods.dev/badge/skills/cdeust/zetetic-team-subagents/normative-design.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.00089 | $0.00702 |
| Opus 5 | $0.00044 | $0.00351 |
| Sonnet 5 | $0.00018 | $0.00140 |
| Haiku 4.5 | $0.00009 | $0.00070 |
Grade A, and why
normative-design 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 11d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Normative Design
Problem shape: a rule, policy, default, or allocation is being designed, applied, or defended, and the load-bearing question is normative rather than technical — who bears the cost, whether the rule determines this case at all, whether responsibility dissolved across a chain of individually-reasonable steps, and whether the arrangement is actually justified or merely inherited.
Relevant geniuses
| Agent | Use when |
|---|---|
| rawls | legitimate values collide (privacy vs security, fairness vs efficiency) — design behind the veil of ignorance, without knowing which party you will be; check the arrangement against the worst-off position |
| hart | a general rule does not clearly determine the specific case — analyze the open texture, reason by precedent, separate the ratio decidendi from what merely accompanied it |
| arendt | systemic harm occurred and no one intended it — audit for suppressed judgment and cog-in-machine structure before attributing malice |
| foucault | the only answer to "why this way?" is "we've always done it this way" — trace the contingent origin of what presents itself as natural; map who the practice makes into what |
Invocation
- Pick the best-fit agent above. If two or more fit, run
tools/genius-invoker.sh route "<problem>"and take the top ranked match. - Load it:
tools/genius-invoker.sh invoke <agent> "<problem>", then readagents/genius/<agent>.mdin full. - Apply the agent's
<workflow>step by step — do not skip steps — and answer in its<output-format>. The deliverable names who bears which cost under the proposed rule, not just that the rule is defensible. - Typical chain: foucault denaturalizes the inherited practice → rawls tests
the replacement behind the veil → hart writes the rule and its exception
structure. Run via
tools/genius-invoker.sh compose foucault rawls hart -- "<problem>". - If no shape above matches, do not force a genius — use a standard team agent (INDEX.md routing rule).
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.
- 11d ago First seen · 53 lines · 89 tokens per session scan A 87d6a8841f45
normative-design is a skill published in the GitHub repository cdeust/zetetic-team-subagents (7 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 702 once invoked, about $0.0004 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
plagiarism-checker
Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.
incorporation
A guide for moving from working as an individual business owner to operating through a company in Japan. It covers company types, setup steps, officer pay, taxes, and social insurance.
revenue-recognition
Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms…
compensation-and-leveling
Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review…
employment-compliance
Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a…
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.