taskcenter AGENTS.md

Project instructions for TaskCenter, a local tool for managing coding tasks and their acceptance. They define privacy rules, required task registration, and checks to run before completion.

In plain words
What is it for?
Guiding agents working on TaskCenter, including task registration, safe file access, and running synchronization, linting, tests, and diff checks.
Why use it?
They prevent session data and credentials from being exposed and ensure claimed work is checked before it is accepted.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/xiaogezi/taskcenter/agents-md
Clone the repo
git clone --depth 1 https://github.com/xiaogezi/taskcenter

Made for: Codex, OpenCode.

Per session 248 This file is loaded in full into every session.
When invoked 248 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00248 $0.00248
Opus 5 $0.00124 $0.00124
Sonnet 5 $0.00050 $0.00050
Haiku 4.5 $0.00025 $0.00025

Measured 2d ago against content hash 8ae8121c7eb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

taskcenter 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 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.

AGENTS.md · 29 lines

What it actually says

TaskCenter Agent Rules

Safety boundaries

  • TaskCenter is a local-only task governance tool. Do not add remote upload of session content without a separate privacy and authentication design.
  • Read Codex session data only from ~/.codex/sessions/**/*.jsonl and ~/.codex/session_index.jsonl.
  • Never read ~/.codex/auth.json, API keys, cookies, or other credentials.
  • Never modify files under ~/.codex; user-owned integration config changes require explicit user action.
  • Treat an assistant's done_claimed status as an implementation claim, not acceptance.

Required workflow

Before changing project files in an MCP-enabled session:

  1. Call taskcenter_session_register with the real session ID, workspace, agent, provider, and model.
  2. Call taskcenter_task_create with a goal, plan, and acceptance criteria.
  3. Continue only after accepted=true and a distinct task_id are returned.

If TaskCenter MCP is unavailable, restrict work to read-only inspection and report TASKCENTER_UNAVAILABLE.

Verification

npm run sync
npm run lint
npm test
git diff --check
Changes

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.

  1. 2d ago First seen · 29 lines · 248 tokens per session scan A 8ae8121c7eb8

Subscribe to this mod's changes

taskcenter AGENTS.md is an instructions file published in the GitHub repository xiaogezi/taskcenter (0 stars, last pushed 19d ago), licensed Apache-2.0. It adds 248 tokens to every session, about $0.0012 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.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens