mKit AGENTS.md

Repository instructions for mKit that tell coding agents how to plan work, follow project rules, and verify changes. They include requirements for plan files and checks before work is accepted.

In plain words
What is it for?
They are for guiding agents working in the mKit codebase, including planning, state tracking, and verification.
Why use it?
They reduce confusion about the repository’s workflow and make the agent follow the project’s required checks.

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/jscraik/mkit/agents-md
Clone the repo
git clone --depth 1 https://github.com/jscraik/mKit

Made for: Codex, OpenCode.

Per session 271 This file is loaded in full into every session.
When invoked 271 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.00271 $0.00271
Opus 5 $0.00135 $0.00135
Sonnet 5 $0.00054 $0.00054
Haiku 4.5 $0.00027 $0.00027

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

Security

Grade A, and why

mKit 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 · 25 lines

What it actually says

mKit Agent Guide

Agent-First Scaffold Contract (managed by ~/.codex)

This repository participates in Jamie's global agent-first scaffold program.

Required global references:

  • /Users/jamiecraik/.codex/instructions/openai-agent-workflow-playbook.md
  • /Users/jamiecraik/.codex/instructions/README.checklist.md
  • /Users/jamiecraik/.codex/instructions/validator-contracts.md
  • /Users/jamiecraik/.codex/instructions/strict-toggle-governance.md
  • /Users/jamiecraik/.codex/instructions/agent-first-scaffold-spec.md

Repo-level requirements:

  • Maintain .agent/PLANS.md using tasks / id / depends_on contract.
  • Validate plan files with: python3 /Users/jamiecraik/.codex/scripts/plan-graph-lint.py <plan-file>
  • Run canonical verification: /Users/jamiecraik/.codex/scripts/verify-work.sh

State model: S0 -> S1 -> S2 -> S3 -> S4 -> S5 with rollback to Sx on critical governance events.

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 · 25 lines · 271 tokens per session scan A da07d5c0f41e

Subscribe to this mod's changes

mKit AGENTS.md is an instructions file published in the GitHub repository jscraik/mKit (1 stars, last pushed 1mo ago), licensed MIT. It adds 271 tokens to every session, about $0.0014 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

react-starter-kit AGENTS.md

AGENTS.md instructions for kriasoft/react-starter-kit, covering monorepo structure, tech stack, commands, database: bun db:{push,generate,migrate,studio,seed,export} and verification.

kriasoft/react-starter-kit · 1,319 tokens

react-starter-kit CLAUDE.md

Claude Code instructions for kriasoft/react-starter-kit, a project described as: Modern React starter kit with Bun, TypeScript, Tailwind CSS, tRPC, Stripe, and Cloudflare Workers. Production-ready monorepo for building fast web apps.

kriasoft/react-starter-kit · 57 tokens

react-starter-kit copilot-instructions.md

Copilot instructions for kriasoft/react-starter-kit: Read AGENTS.md in the repository root and any subdirectory AGENTS.md files for project context, conventions, and architecture details before making changes.

kriasoft/react-starter-kit · 29 tokens

node-typescript-boilerplate AGENTS.md

Instructions for jsynowiec/node-typescript-boilerplate, covering agents.md, ground rules (always), typescript, node.js and testing (vitest).

jsynowiec/node-typescript-boilerplate · 543 tokens

expo_boilerplate CLAUDE.md

Instructions for chohra-med/expo_boilerplate, covering claude.md — mobilelauncher lt, 🌿 branches — the trunk is development, there is no main, project skill, what this project is and the master rules.

chohra-med/expo_boilerplate · 782 tokens

expo_boilerplate AGENTS.md

Instructions for chohra-med/expo_boilerplate, covering agents.md — mobilelauncher lt, project and 🎯 the master rules location.

chohra-med/expo_boilerplate · 345 tokens