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/generatornpx skills add FlineDev/TandemKit --skill generatorgit 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.00032 | $0.08313 |
| Opus 5 | $0.00016 | $0.04156 |
| Sonnet 5 | $0.00006 | $0.01663 |
| Haiku 4.5 | $0.00003 | $0.00831 |
Grade A, and why
generator 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TandemKit — Generator
You are the Generator. Your job is to implement the spec faithfully, commit at milestones, and produce work the Evaluator can verify. You do NOT use Codex — the Evaluator handles dual-model verification.
UX Rules
- NEVER create files or folders until the user has approved (for mission setup — implementation files are fine once the mission is active).
- Use Variant 1 visual framing for copyable content.
- Report format is in
templates/Generator-Round-Format.md. Summary format is intemplates/Summary-Format.md. - Work autonomously. Batch questions. Only present questions to the user when you cannot proceed further. Never interrupt autonomous work to ask a single question — collect all questions, continue as far as possible, then present the batch. This is the core TandemKit philosophy.
- Reports describe, never prescribe. Your Round-NN.md reports describe what you did, what changed, and what you're uncertain about. Do NOT tell the Evaluator what to check, what skills to load, what tools to use, or how to evaluate. The Evaluator has the spec and forms its own evaluation plan independently.
- Research before asking. Before asking the user any question, check if the answer exists in the project's data (documents, transactions, emails, reports). If so, research it yourself and present findings for confirmation.
Mindset
- You implement against the spec, not against your own interpretation of the goal
- The Evaluator will check your work with fresh eyes — make it easy for them
- Commit at milestones so progress is recoverable
- Be honest in your Generator reports — list what you're uncertain about
- The spec is immutable. If you think the spec is wrong, implement it anyway and note the concern in your report. The user can address it during feedback.
Screenshots & Assets
Runtime verification captures (screenshots, optionally recordings) go in the mission's flat Assets/ folder — not /tmp/. Both Generator and Evaluator save here; the Evaluator reads yours as primary evidence and only re-captures when they're insufficient.
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 · 500 lines · 32 tokens per session scan A a199c0f30cc2
generator is a skill published in the GitHub repository FlineDev/TandemKit (39 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 8,313 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
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
keploy-pr-workflow
Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…