agentmods.dev

agent-context-kit AGENTS.md

A set of instructions for coding agents working on the AgentContextKit TypeScript and Node.js project. It defines which project documents to read, how to work, and which releases require explicit user permission.

In plain words
What is it for?
Use it when maintaining AgentContextKit, checking its code, following its documentation-first process, or preparing a release-related change.
Why use it?
It gives agents a consistent workflow and prevents unauthorized publishing, merging, tagging, or deployment. It also identifies the correct command-line tool for verification.

Instructions file for CodexOpenCode

14 3d ago A scan 1,170 tokens original MIT
View the source file Cynrath/agent-context-kit
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/cynrath/agent-context-kit/agents-md
Clone the repo
git clone --depth 1 https://github.com/Cynrath/agent-context-kit

Made for: Codex, OpenCode.

Per session 1,170 This file is loaded in full into every session.
When invoked 1,170 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.01170 $0.01170
Opus 5 $0.00585 $0.00585
Sonnet 5 $0.00234 $0.00234
Haiku 4.5 $0.00117 $0.00117

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

Security

Grade A, and why

agent-context-kit 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 · 87 lines

How it starts

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

AGENTS.md — AgentContextKit v0.2.0

AgentContextKit (ackit, TypeScript + Node.js + npm) is feature-complete on master and ships as the scoped npm package @cynrath/agent-context-kit 0.2.0 (CLI binary ackit). The repository's own docs are the single source of truth for agents.

Controlled-release governance

Release actions are user-authorized, not agent-authorized:

  • master push/merge, npm publish, tag creation/movement, and GitHub Releases may be performed only inside a task that carries explicit user authorization for that exact action. Absent that authorization in the active task, they are prohibited — do not infer it from past tasks or this document.
  • Always prohibited: force-push, rebase, history rewrite, tag movement/deletion, workflow dispatch, deployments.
  • The frozen legacy .NET line stays immutable everywhere: published NuGet versions/tags/releases (1.0.0-rc.1, earlier alphas) are untouchable; no NuGet or .NET release pipeline exists or may be created for vNext.
  • The old global .NET ackit tool must not be used as a validation tool; all verification uses the repository-built CLI (see below).

Canonical entry points (read in this order)

  1. AGENTS.md, CLAUDE.md, .github/copilot-instructions.md — current governance (this file is authoritative)
  2. The current active task under docs/tasks/active/
  3. docs/v0.2.0/REQUIREMENTS.md, docs/v0.2.0/TRACEABILITY.md, docs/v0.2.0/ROADMAP.md, docs/v0.2.0/EXECUTION_PLAN.md — v0.2.0 canonical contract
  4. docs/decisions/ADR-0015..0024 (v0.2.0) + docs/decisions/ADR-0001..0014 (baseline, reused)
  5. docs/rebuild/ — historical vNext Goal-2 evidence, preserved verbatim (not active)
  6. Decisions: docs/decisions/

ACKit-first / task-first / docs-first workflow

  • New work requires a task doc created with the repository's own tool: node dist/cli/index.js task "<title>". Never invent task IDs.
  • Exactly one active checklist item at a time: [ ] pending, [~] active, [x] completed+verified, [!] blocked.
  • Complete a task only with real evidence recorded in its Completion notes; then a focused Conventional Commit; then immediately continue with the next dependency-ready task.

Read the full file on GitHub · 87 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. 2d ago First seen · 87 lines · 1,170 tokens per session scan A ca01c9c02ff2

Subscribe to this mod's changes

agent-context-kit AGENTS.md is an instructions file published in the GitHub repository Cynrath/agent-context-kit (14 stars, last pushed 3d ago), licensed MIT. It adds 1,170 tokens to every session, about $0.0059 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-30.

Git and workflowSecurityWriting and docsagents-mdclicodexcoding-agentsdeveloper-toolsrepository-scanner
Related

Other instructions, from other repositories

repository-harness AGENTS.md

Instructions for hoangnb24/repository-harness, covering agent instructions and harness.

hoangnb24/repository-harness · 332 tokens

repository-harness CLAUDE.md

Instructions for hoangnb24/repository-harness, covering project rules and harness.

hoangnb24/repository-harness · 61 tokens

boring-is-all-you-need AGENTS.md

Instructions for Khalilzhang0825/boring-is-all-you-need, covering agents.md - boring is all you need codex guide, project intent, working rules, validation and release discipline.

Khalilzhang0825/boring-is-all-you-need · 422 tokens

AGENTS.md AGENTS.md

Instructions for Anbeeld/AGENTS.md, covering global instructions, priorities, boundaries, uncertainty and evidence.

Anbeeld/AGENTS.md · 1,964 tokens

vibe-coding-repository-standard AGENTS.md

Instructions for cz1993/vibe-coding-repository-standard, covering vcrs repository instructions, purpose, communication, change discipline and privacy and safety.

cz1993/vibe-coding-repository-standard · 646 tokens

AgentRules AGENTS.md

Instructions for LearnAIHubC/AgentRules, covering agents.md, 1. think before coding, 2. simplicity first, 3. preserve existing architecture and framework boundaries and 4. surgical changes.

LearnAIHubC/AgentRules · 1,280 tokens