takt: Instructions file for Codex

AGENTS.md

takt AGENTS.md is an instructions file for Codex, OpenCode from nrslib/takt. It costs 1,020 tokens per session, scanned A, original, MIT.

Repository instructions for Takt, a TypeScript command-line tool with core workflows, built-in assets, documentation, and automated tests.

In plain words
What is it for?
Use them when adding features or modules, changing the CLI, updating built-in workflows, or running unit, integration, and end-to-end tests.
Why use it?
They explain where different parts of the code live and which commands build, lint, watch, and test the project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is nrslib/takt's own configuration. It tells Codex and OpenCode how to work on takt itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything takt configures →

View source ↗ nrslib/takt
About the project

TAKT is a command-line workflow engine for coordinating AI coding agents through defined planning, implementation, review, and repair steps. Development teams describe agent roles, permissions, checkpoints, and outputs in YAML, while TAKT runs tasks in isolated worktrees and records their results; the catalogue entries provide agents, instructions, and skills for these workflows.

nrslib/takt · 1,423 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to nrslib/takt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nrslib/takt/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/nrslib/takt

Made for: Codex, OpenCode.

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

agentmods badge for takt AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nrslib/takt/agents-md/github.svg)](https://agentmods.dev/instructions/nrslib/takt/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/nrslib/takt/agents-md"><img src="https://agentmods.dev/badge/instructions/nrslib/takt/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.

agentmods 80×15 button for takt AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/nrslib/takt/agents-md"><img src="https://agentmods.dev/badge/instructions/nrslib/takt/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,020 This file is loaded in full into every session.
When invoked 1,020 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01020 $0.01020
Opus 5.5 $0.00408 $0.00408
Sonnet 5.5 $0.00204 $0.00204
Haiku 4.5 $0.00102 $0.00102

Measured 14d ago against content hash 491f21559698, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

takt 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 14d 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 · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

  • src/: main TypeScript source. CLI entrypoints live in src/app/cli/, core workflow execution in src/core/, shared helpers in src/shared/, and feature modules in src/features/.
  • src/__tests__/: Vitest unit and integration tests, typically named *.test.ts.
  • e2e/: end-to-end specs, helpers, fixtures, mock workflows, and provider scenarios.
  • builtins/: builtin workflows, facets, templates, prompts, and runtime config assets shipped with the CLI.
  • docs/: user and design documentation. bin/ contains executable wrappers. dist/ is generated output and should not be edited by hand.

Build, Test, and Development Commands

  • npm install: install project dependencies.
  • npm run build: compile TypeScript and copy runtime prompts, i18n files, and presets into dist/.
  • npm run watch: run the TypeScript compiler in incremental watch mode.
  • npm run lint: run ESLint on src/.
  • npm test: run the fast unit gate in an adaptive number of concurrent shards during development (based on available parallelism, capped at 8). Integration tests are excluded; targeted source tests are routed to their classified runner.
  • npm run test:it: run the light integration gate after implementation. It covers real filesystem, bounded storage, and multi-component contracts.
  • npm run test:it:heavy: run all child-process, Git, full-engine, and measured resource-heavy integration tests locally with one worker. Pull-request CI splits it across isolated runners; do not run it routinely during development.
  • npm test -- <test-file>: run a classified test through its unit, light-IT, or heavy-IT runner. When adding or changing an IT, also run npm test -- src/__tests__/releaseVerificationWiring.test.ts by itself. Always run an added or changed heavy IT before handoff; the PR-wide heavy gate is not its first execution.
  • npm run test:e2e:smoke: run the focused mock E2E suite during development.
  • npm run check:release: run the full release verification path locally: dependency sync (sync:nix-deps, rewrites package-lock.json / flake.nix and reinstalls), build, packed global install with npm 10 and 11 (test:global-install), lint, fast unit (adaptive local shards), light IT, heavy IT, and all E2E suites. The 8-runner unit matrix is a separate path in the main pull-request CI workflow.

Read the full file on GitHub · 46 lines

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. 14d ago Changed · +43 tokens per session 491f21559698
  2. 1mo ago First seen · 46 lines · 977 tokens per session scan A 42e8339022c3

Subscribe to this mod's changes

takt AGENTS.md is an instructions file published in the GitHub repository nrslib/takt (1,423 stars, last pushed today), licensed MIT. It adds 1,020 tokens to every session, about $0.0041 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.

Related

Other instructions, from other repositories