Codex Taskboard is a local-first issue board that runs in a browser and can be embedded in Codex through a launcher or injection script. Developers use its web interface, HTTP API, and taskctl command-line tool to manage coding tasks, while its bundled skill guides Codex through task status changes and verification. The catalogue entries provide the task-management instruction and skill used by Codex.
Borrowing it
Nothing to install: this file belongs to chuspeeism/dashi-taskboard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chuspeeism/dashi-taskboard/main/AGENTS.mdgit clone --depth 1 https://github.com/chuspeeism/dashi-taskboardWrote 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/instructions/chuspeeism/dashi-taskboard/agents-md)<a href="https://agentmods.dev/instructions/chuspeeism/dashi-taskboard/agents-md"><img src="https://agentmods.dev/badge/instructions/chuspeeism/dashi-taskboard/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/chuspeeism/dashi-taskboard/agents-md"><img src="https://agentmods.dev/badge/instructions/chuspeeism/dashi-taskboard/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.04429 | $0.04429 |
| Opus 5.5 | $0.01772 | $0.01772 |
| Sonnet 5.5 | $0.00886 | $0.00886 |
| Haiku 4.5 | $0.00443 | $0.00443 |
Grade A, and why
dashi-taskboard AGENTS.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 1mo 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Development Rules
For feature work in this repository, use this order:
- Before implementation, prove the real operation path to the user: entry point → user or agent action → data change or other side effect → observable result. Cite the actual component, API, and file involved, or demonstrate the path in the product. This proof is not a test.
- Implement the requested main path with the smallest direct change that makes it work.
- After implementation, demonstrate or verify only that direct operation path and give the result to the user for confirmation.
- Before the user confirms the feature works, do not proactively add guardrails, mutation or regression tests, legacy compatibility protection, defensive extensions, or speculative fallback behavior.
- User confirmation does not automatically authorize that follow-up work. Add targeted protection or tests only when the user explicitly asks for them, or when the user reports a concrete failure scenario that requires them.
The primary objective is to make the requested function work. Focus on the feature implementation itself and avoid over-design; safety, guardrails, and testing must not dominate the work or turn the feature into a surrounding engineering project.
This ordering does not waive higher-priority safety or security requirements. Keep validation that is necessary at real external boundaries, such as user input or external APIs, but do not expand it into hypothetical protection beyond the requested path.
Taskboard Delivery Workflow
Use this workflow when the user asks to process Taskboard work.
1. Read and claim work
- Read only the Taskboard states that the user asked to process. For the normal development flow, claim
todoitems and continue unfinishedin_progressitems. - Never assign
backlogitems. Leave an item unclaimed when its description or latest comment explicitly requires waiting. - Read the full issue description, attachments, and all comments before routing or changing it.
- GitHub Issue and PR synchronization is not a default step. Read or synchronize GitHub Issue/PR data only when the user explicitly requests it.
- Use the packaged or injected
taskctland the exact active Taskboard runtime. Do not fall back to a global CLI, a guessed port, or another data source.
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.
- 1mo ago Changed · +2 lines · +114 tokens per session 6db0a3cb5de0
- 1mo ago First seen · 196 lines · 4,315 tokens per session scan A af4333627cc5
dashi-taskboard AGENTS.md is an instructions file published in the GitHub repository chuspeeism/dashi-taskboard (3,403 stars, last pushed 6d ago), licensed Apache-2.0. It adds 4,429 tokens to every session, about $0.0177 per session on Opus 5.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 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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.