agentmods.dev

cli AGENTS.md

Repository instructions for releasing the tako-cli package through GitHub Actions, the automated workflow service built into GitHub.

In plain words
What is it for?
Following the build and test checks, running the release script, watching the GitHub Actions workflow, and confirming the new npm package version.
Why use it?
They prevent accidental local publishing and make the required checks and release steps clear.

Instructions file for CodexOpenCode

3 2d ago A scan 317 tokens original MIT
View the source file tako-dev/cli
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/tako-dev/cli/agents-md
Clone the repo
git clone --depth 1 https://github.com/tako-dev/cli

Made for: Codex, OpenCode.

Per session 317 This file is loaded in full into every session.
When invoked 317 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.00317 $0.00317
Opus 5 $0.00159 $0.00159
Sonnet 5 $0.00063 $0.00063
Haiku 4.5 $0.00032 $0.00032

Measured yesterday against content hash 5970eae1ed93, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cli 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 yesterday.

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

What it actually says

Agent Instructions

Release And Publishing

tako-cli must be published through GitHub Actions. Never run npm publish manually from a local machine.

Normal release flow:

  1. Start from a clean, current main.

  2. Run validation before releasing:

    bun run build
bun test tests/pre-release.test.ts

    Also run focused tests for the code path being released.

  3. Run the repository release script:

    bun run release

    This is only the CI trigger. It bumps package.json, commits chore: release vX.Y.Z, creates tag vX.Y.Z, pushes main, and pushes tags.

  4. Watch the GitHub Actions workflow CLI release triggered by the v* tag:

    gh run list --repo tako-dev/cli --workflow "CLI release" --limit 5
gh run watch <run-id> --repo tako-dev/cli --exit-status

  5. Only call the release complete after both checks pass:

    gh run view <run-id> --repo tako-dev/cli --json status,conclusion
npm view tako-cli version dist-tags.latest --registry=https://registry.npmjs.org/ --json

The actual npm publish happens in GitHub Actions with OIDC trusted publishing. See docs/release/RUNBOOK.md for the full runbook and recovery steps.

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. yesterday First seen · 46 lines · 317 tokens per session scan A 5970eae1ed93

Subscribe to this mod's changes

cli AGENTS.md is an instructions file published in the GitHub repository tako-dev/cli (3 stars, last pushed 2d ago), licensed MIT. It adds 317 tokens to every session, about $0.0016 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.

Git and workflowProductivityTesting
Related

Other instructions, from other repositories

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

buildNext

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

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

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

spec-kit 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,040 tokens

langchain 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