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 Maxmedawar/tandem --skill tandem-agentic-engineeringgit clone --depth 1 https://github.com/Maxmedawar/tandemWrote 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/maxmedawar/tandem/tandem-agentic-engineering)<a href="https://agentmods.dev/skills/maxmedawar/tandem/tandem-agentic-engineering"><img src="https://agentmods.dev/badge/skills/maxmedawar/tandem/tandem-agentic-engineering.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.1 | $0.00164 | $0.02587 |
| Opus 5 | $0.00082 | $0.01293 |
| Sonnet 5 | $0.00033 | $0.00517 |
| Haiku 4.5 | $0.00016 | $0.00259 |
Grade B, and why
tandem-agentic-engineering scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Recommended:** alias `claude='claude --model opus'`. **Never** force the model globally in `~/.claude/settings.json` — that drags every throwaway session onto the big model too. Per-session via the launch flag wins. How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tandem Agentic Engineering
🦔🦔🦔🦔🦔 — When you see this, agentic engineering mode is active.
Start EVERY response in this workflow with 🦔🦔🦔🦔🦔.
This is how the worker layer of tandem works. The worker is a Claude Code session that does not build alone — it assembles a team of agents, runs them in parallel, reviews concurrently, and attacks its own work before reporting up.
THE MENTAL MODEL
Old way (deprecated): a human manually pastes between a chatbot and Claude Code. Manual middleman. Slow.
Agentic way: the chatbot (director) is the strategic brain. Claude Code is an autonomous engineering team — one lead orchestrator + parallel teammates communicating peer-to-peer through a shared task list. The human stops being the middleman.
The worker's role:
- Assemble the right team for the task.
- Run implementers, a concurrent reviewer, and a test writer in parallel.
- Attack the result with adversarial agents, then fix what they find.
- Report up only when it can't improve the work further.
No manual paste-back loops between every turn. The team executes autonomously and reports up.
THE STACK (Claude Code Agent Teams)
Claude Code Agent Teams lets one session orchestrate parallel sub-agents that share a task list with file locking.
Typical roster (use what fits the task):
Orchestration:
agent-organizer— picks the right specialists, builds the teammulti-agent-coordinator— runs N agents concurrently, shared state + failure handlingworkflow-orchestrator— stateful processes, transactions, error recoverytask-distributor— work queue / load balancingcontext-manager— shared memory + data sync between agents
Research:
research-analyst— multi-source research -> synthesissearch-specialist— precise retrieval, query optimizationmarket-researcher,competitive-analyst,trend-analyst,data-researcher,project-idea-validator— domain research and brutal-honesty pressure-testing
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.
- 8d ago First seen · 181 lines · 164 tokens per session scan B 0e5bfb040193
tandem-agentic-engineering is a skill published in the GitHub repository Maxmedawar/tandem (25 stars, last pushed 26d ago), licensed MIT. It adds 164 tokens to every session and 2,587 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
adk-unit-design
Writes an as-built architecture document for one ADK code unit — purpose, execution flow, data flow, cross-class dependencies, extension points, and the parts that must not change — to docs/design/{topic}/{unit}/index.md. It describes the code as implemented, not a proposed design, and its reader is a developer about…
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
explain-for
Explain a topic, a piece of code, an error, or a design decision calibrated to one named audience — a 5-year-old, a 5th grader, a manager, a designer, a graduate student, a parent. Resolves who the explanation is for (from the request, or from what memory already records about that person), establishes the ground…
web-verify
Look at your OWN front-end change before claiming it works -- navigate the loopback URL of a dev server or pod you started, screenshot the surface you changed, read the image to judge it, and embed it in chat. Three capture backends: playwright-cli (the session the dashboard Browser panel shows), the agent-browser CLI…
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.