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 instructions/davecodev/tinkertasker/claude-mdgit clone --depth 1 https://github.com/DaveCoDev/TinkerTaskerWhat 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.01000 | $0.01000 |
| Opus 5 | $0.00500 | $0.00500 |
| Sonnet 5 | $0.00200 | $0.00200 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
TinkerTasker CLAUDE.md 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project README
@README.md
Project Structure
TinkerTasker is broken up into two main components:
ai-core: Contains the core AI functionality, including the MCP servers for filesystem and web.
This is the pyproject.toml for the package
@./ai-core/pyproject.toml
cli-ux: Provides the command-line interface for interacting with TinkerTasker.
This is the pyproject.toml for the package
@./cli-ux/pyproject.toml
Core Design Principles
Ruthless Simplicity
- KISS principle taken to heart: Keep everything as simple as possible, but no simpler
- Minimize abstractions: Every layer of abstraction must justify its existence
- Start minimal, grow as needed: Begin with the simplest implementation that meets current needs
- Avoid future-proofing: Don't build for hypothetical future requirements
- Question everything: Regularly challenge complexity in the codebase
Architectural Integrity with Minimal Implementation
- Preserve key architectural patterns: MCP for service communication, SSE for events, separate I/O channels, etc.
- Simplify implementations: Maintain pattern benefits with dramatically simpler code
- Scrappy but structured: Lightweight implementations of solid architectural foundations
- End-to-end thinking: Focus on complete flows rather than perfect components
Library Usage Philosophy
- Use libraries as intended: Minimal wrappers around external libraries
- Direct integration: Avoid unnecessary adapter layers
- Selective dependency: Add dependencies only when they provide substantial value
- Understand what you import: No black-box dependencies
Testing Strategy
- Emphasis on integration and end-to-end tests
- Manual testability as a design goal
- Focus on critical path testing initially
- Add unit tests for complex logic and edge cases
Areas to Embrace Complexity
Some areas justify additional complexity:
- Security: Never compromise on security fundamentals
- Data integrity: Ensure data consistency and reliability
- Core user experience: Make the primary user flows smooth and reliable
- Error visibility: Make problems obvious and diagnosable
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 · 88 lines · 1,000 tokens per session scan A fdf884d0819a
TinkerTasker CLAUDE.md is an instructions file published in the GitHub repository DaveCoDev/TinkerTasker (5 stars, last pushed 1y ago), licensed MIT. It adds 1,000 tokens to every session, about $0.0050 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 instructions, from other repositories
Ageniti AGENTS.md
Instructions for Ageniti/Ageniti, covering ageniti, what ageniti is, core model, canonical import and minimal pattern.
spellbook AGENTS.md
Instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.
open-supermarkets AGENTS.md
Instructions for abracadabra50/open-supermarkets, covering agent integration guide, supported frameworks, quick integration, 1. add as skill and 2. agent calls commands.
helm copilot-instructions.md
Instructions for PetePeter/helm, covering gamepad-cli-hub — copilot instructions, project purpose, system overview, data flow pipeline and key controls.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
fusion-skills AGENTS.md
AGENTS.md instructions for CrowdStrike/fusion-skills, covering agents.md, what this is, prerequisites, repository structure and skills ecosystem.