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/smekai/taskplanner/claude-mdgit clone --depth 1 https://github.com/smekai/taskplannerWhat 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.02942 | $0.02942 |
| Opus 5 | $0.01471 | $0.01471 |
| Sonnet 5 | $0.00588 | $0.00588 |
| Haiku 4.5 | $0.00294 | $0.00294 |
Grade A, and why
taskplanner 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 3d 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.
This is a copy
95% identical to taskplanner AGENTS.md — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TaskPlanner — Development Guide
What is this?
TaskPlanner is a VS Code extension that provides markdown-based task tracking directly in your project folder. Think lightweight Jira — but stored as .md files, git-tracked, and AI-agent friendly.
Tech Stack
- Language: TypeScript (strict mode)
- Bundler: esbuild
- Unit tests: Vitest (
npm test) - Integration tests: @vscode/test-cli
- Linter: ESLint (
npm run lint) - Formatter: Prettier (
npm run format)
Project Structure
src/core/— Pure logic, zero VS Code dependencies. Models, parser, serializer, stores, config.src/extension/— VS Code extension shell. Commands, views, providers, watchers.src/test/core/— Vitest unit tests for core library.src/test/extension/— VS Code integration tests.resources/— SVG icons and templates.plugins/taskplanner/— Shared Cursor/Codex plugin source, manifests, skills, and runtime.packages/mcp-server/— npm package@smekai/taskplanner. Manifest, bin launcher, and README only; the bundle and board UI are copied in byesbuild.jsfrom the same build as the plugin.dist/— Generated extension output and channel-specific release packages.
Key Commands
npm install # Install dependencies
npm run build # Production build (esbuild)
npm run watch # Dev build with watch mode
npm test # Run unit tests (Vitest)
npm run lint # Run ESLint
npm run format # Run Prettier
npm run package # Create dist/vscode/taskplanner-<version>.vsix
Task File Format
Tasks are stored in .tasks/ as markdown files (BACKLOG.md, NEXT.md, IN_PROGRESS.md, DONE.md). Each task is a ## section:
## TASK-001: Task title here
**Priority:** P1
**Tags:** tag1, tag2
Description text in markdown.
---
Changelog
When you move a task to Done, add an entry to CHANGELOG.md under the ## [Unreleased] section. Use the appropriate subsection (Added, Changed, Fixed, Removed) and reference the task ID. Keep entries concise — one line per change, written from the user's perspective.
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.
- 3d ago First seen · 265 lines · 2,942 tokens per session scan A d55dd9dca928
taskplanner CLAUDE.md is an instructions file published in the GitHub repository smekai/taskplanner (19 stars, last pushed 5d ago), licensed MIT. It adds 2,942 tokens to every session, about $0.0147 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to taskplanner AGENTS.md, differing in 1 line, and is treated as a copy.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.