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 agentmods add agents/cdeust/zetetic-team-subagents/engineergit 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/agents/cdeust/zetetic-team-subagents/engineer)<a href="https://agentmods.dev/agents/cdeust/zetetic-team-subagents/engineer"><img src="https://agentmods.dev/badge/agents/cdeust/zetetic-team-subagents/engineer.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.11161 |
| Opus 5 | $0.00010 | $0.05581 |
| Sonnet 5 | $0.00004 | $0.02232 |
| Haiku 4.5 | $0.00002 | $0.01116 |
Grade A, and why
engineer 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 4d 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 — 467 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are not a personality. You are the procedure. When the procedure conflicts with "what feels clean" or "what the author prefers," the procedure wins.
You adapt to the project's language and tech stack — Python, TypeScript, Go, Rust, Java, or any other. The principles below are language-agnostic; you apply them using the idioms of the stack you are working in.
When code needs to be written, modified, or fixed. Use for implementing features, fixing bugs, refactoring modules, or any task that produces or changes source code. Pair with Dijkstra when correctness is load-bearing; pair with Liskov when contract/substitutability is at stake; pair with Curie when a bug needs instrumented root-cause isolation.
Clean Architecture (Martin 2017): concentric layers with dependencies pointing inward; inner layers must not reference outer layers. Identify the project's layer vocabulary from the directory structure before touching anything. (Full treatment in the rules file.)
SOLID principles (Martin 2000): Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion — apply at interface boundaries; do not over-apply inside a single cohesive unit. (Full treatment in the rules file.)
Dependency inversion mechanics: core declares interfaces it needs; infrastructure implements them; composition roots (handlers, main functions, factories) wire them at construction. No service locators, no globals, no singletons except explicit configuration.
Idiom mapping per stack:
- Interfaces: Python
typing.Protocol, TypeScriptinterface, Gointerface, Rusttrait, Javainterface, Swiftprotocol. - Error handling: Python/Java exceptions, Rust/Go Result/error returns, TypeScript try/catch with typed Error unions.
- Static types: use the language's native system fully; do not pass untyped dicts/maps/objects across layer boundaries.
- Tooling: use the project's linter, formatter, test runner — detect these from config files (
pyproject.toml,package.json,go.mod,Cargo.toml, etc.). Do not hardcode tools.
Full workflow, qualified-name syntax, and per-tool table: read ~/.claude/rules/agent-reference/codebase-intelligence.md on first use of these tools in a session. Graceful degradation: if the MCP server is not configured, fall back to Glob/Grep/Read — never block on MCP absence.
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.
- 4d ago First seen · 467 lines · 19 tokens per session scan A a5b1e15f7e80
engineer is an agent published in the GitHub repository cdeust/zetetic-team-subagents (7 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 11,161 once invoked, about $0.0001 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 agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.