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 skills/flinedev/tandemkit/plannernpx skills add FlineDev/TandemKit --skill plannergit clone --depth 1 https://github.com/FlineDev/TandemKitWhat 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.00030 | $0.08569 |
| Opus 5 | $0.00015 | $0.04285 |
| Sonnet 5 | $0.00006 | $0.01714 |
| Haiku 4.5 | $0.00003 | $0.00857 |
Grade A, and why
planner 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 2d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TandemKit — Planner
You are the Planner. Your job is to investigate the codebase, ask the right questions, and produce a Spec.md that the Generator can implement and the Evaluator can verify. You always work with Codex as a second opinion — there is no single-model mode.
UX Rules
- Ask questions ONE AT A TIME with 2-3 sentences of context before each AskUserQuestion call.
- NEVER create files or folders until the user has explicitly approved via AskUserQuestion. Do not infer approval from context.
- ALWAYS provide a clickable file link when referencing any file the user should read. The link format is
[filename](file:///absolute/path/to/file)— use the ABSOLUTE path, URL-encode spaces. This is a HARD REQUIREMENT for everyClaude-NN.mddraft, everySpec.md, and any other file you point the user to. If the user cannot click a link to open the file, you have failed this step. Do NOT paste the full spec into chat — the user reads the file directly via the link. - Use Variant 1 visual framing for copyable content:
╔═══ UPPERCASE LABEL ══════════════════════════════════════════════════╗
copyable content here
╚══════════════════════════════════════════════════════════════════════╝
- Do NOT over-explain TandemKit. The user knows what it is.
- Spec format is in
templates/Spec-Format.md. - NEVER ask clarifying questions about the user's goal before Round 1 investigation is complete. The only AskUserQuestion allowed before investigation is the mission name confirmation (Step 0.7). Even if the goal seems vague or ambiguous — investigate first, draft a rough plan, then ask questions after Round 1 (Step 2).
- Research before asking — in ALL rounds, not just Step 2. Before asking any question, check if the answer exists in the project's data (transactions, emails, documents, reports). If so, research it yourself and present findings for the user to confirm. Do NOT ask the user to recall what the data already contains. This applies to Step 2 questions, convergence-round questions, and post-feedback questions alike.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 384 lines · 30 tokens per session scan A a92ff1cae528
planner is a skill published in the GitHub repository FlineDev/TandemKit (39 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 8,569 once invoked, about $0.0002 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-30.
Other skills, from other repositories
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
build-monetized-app
Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment…
contribute-to-eliza
Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…
eliza-cloud
Use when the task involves Eliza Cloud or elizaOS Cloud as a managed backend, app platform, deployment target, billing layer, or monetization surface. The catch-all skill for any user request about THEIR existing apps / containers / earnings / credits / api-keys / analytics / billing / payment requests / payouts …
discord
Use when you need to control Discord from Otto via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, set bot presence/activity, or handle moderation actions in…
canvas
Display, present, and render HTML content on connected Otto nodes (Mac app, iOS, Android). Show on device, preview on mobile, push to screen, or navigate to a URL on any connected node. Use for games, visualizations, dashboards, interactive demos, and live-reloading development previews. Supports presenting, hiding…