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 experience-and-transmissiongit 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/experience-and-transmission)<a href="https://agentmods.dev/skills/cdeust/zetetic-team-subagents/experience-and-transmission"><img src="https://agentmods.dev/badge/skills/cdeust/zetetic-team-subagents/experience-and-transmission/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/experience-and-transmission"><img src="https://agentmods.dev/badge/skills/cdeust/zetetic-team-subagents/experience-and-transmission.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.00077 | $0.00779 |
| Opus 5 | $0.00039 | $0.00390 |
| Sonnet 5 | $0.00015 | $0.00156 |
| Haiku 4.5 | $0.00008 | $0.00078 |
Grade A, and why
experience-and-transmission 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.
Experience and Transmission
Problem shape: correctness is not the bottleneck — arrival is. The system passes its tests and fails its user, the documentation exists and is not read, the code runs and cannot be maintained, or the thing being studied changes because the studier is part of it. The deliverable is comprehension and use, measured on the receiving end rather than asserted on the producing end.
Relevant geniuses
| Agent | Use when |
|---|---|
| jobs | the product "works" per component metrics but the integrated experience is broken — treat the whole experience as the spec, hunt the seams, edit ruthlessly rather than add |
| vygotsky | onboarding is too slow or too overwhelming, or documentation exists and nobody reads it — locate the zone of proximal development, scaffold inside it, and plan the fading; diagnose the misconception rather than repeating the explanation |
| varela | the observer cannot be separated from the system studied (UX research where the experience is the product, dogfooding, introspective debugging) — run trained first-person observation and third-person measurement concurrently and report their mutual constraints |
| knuth | the program is correct and unreadable — literate programming, writing for the human reader first; and building the tool before using it when no adequate one exists. Entry point is transmission, not performance: for profiling and optimization work, knuth is routed via the performance path, not this shape |
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 and answer in its<output-format>. The evidence must come from the receiving end — an observed user, a real ramp-up, a maintainer who was not the author. A claim that something "is clear" asserted by its own author does not satisfy this shape. - Typical chain: varela gathers first-person data without pretending the
observer is outside → jobs specifies the integrated experience from it →
vygotsky sequences the scaffolding that gets people there. Run via
tools/genius-invoker.sh compose varela jobs vygotsky -- "<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.
- 12d ago First seen · 55 lines · 77 tokens per session scan A 7fa798ccb490
experience-and-transmission is a skill published in the GitHub repository cdeust/zetetic-team-subagents (7 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 779 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
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
examples
Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
learning-and-development
Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.
onboard
Quick protocol recommendation from recent sessions, or quest-based learning through scenario, trial, and quiz.
vertical-real-estate
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…
engineering-onboarding
Create an onboarding guide for an engineer joining a team that consumes the design system. Trigger when someone says: onboard new engineer, developer getting started guide, new engineer guide, engineering onboarding, first day for developers, frontend onboarding, or anything about helping an engineer new to the team…