agentmods.dev

Agent-Skills: Instructions file for Codex

AGENTS.md

Agent-Skills AGENTS.md is an instructions file for Codex, OpenCode from jscraik/Agent-Skills. It costs 1,512 tokens per session, scanned A, original, Apache-2.0.

A guide for working in Agent-Skills Kit, a repository that manages reusable instructions and workflows for coding agents.

In plain words
What is it for?
Use it when bootstrapping the repository, inspecting YAML, running infrastructure tests, or changing skills, workflows, and agent documentation.
Why use it?
It explains the project’s required setup, command wrappers, configuration checks, and test environment so agents use the repository’s supported tools.

Instructions file for CodexOpenCode

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

This is jscraik/Agent-Skills's own configuration. It tells Codex and OpenCode how to work on Agent-Skills 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 Agent-Skills configures →

not rated 9repo changed 1mo ago A scan 1,512 tokens original Apache-2.0
View source ↗ jscraik/Agent-Skills
Reuse

Borrowing it

Nothing to install: this file belongs to jscraik/Agent-Skills. 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/jscraik/Agent-Skills/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/jscraik/Agent-Skills

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 Agent-Skills AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jscraik/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/jscraik/agent-skills/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,512 This file is loaded in full into every session.
When invoked 1,512 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.01512 $0.01512
Opus 5.5 $0.00605 $0.00605
Sonnet 5.5 $0.00302 $0.00302
Haiku 4.5 $0.00151 $0.00151

Measured 1mo ago against content hash d563906119bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Agent-Skills 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 1mo 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 · 112 lines

How it starts

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

agent-skills Agent Guide

Agent-Skills is a transitional migration repository. The approved lifecycle is Foundry holding -> SDK checking and preparation -> private Tessl registry -> Codex runtime installation, with verified OpenAI-provider exemptions. Complete that lifecycle and repository independence before refining either product.

Jamie approved a bounded transitional exception on 2026-09-27: the selected existing custom skills may run from ~/.agents/skills without prior SDK/Tessl processing until SDK supports the required workflows. They remain unchecked, not SDK-cleared. This does not cover plugins or new external intake. Follow the selected-set and preservation rules.

Root Essentials

  • On a fresh checkout, run bash scripts/bootstrap-ask.sh --json before requiring ./bin/ask; if the wrapper is unavailable, verify the fallback with python3 bin/ask repo status --json.
  • Use ./bin/ask for repo operations; it forwards to Infrastructure/bin/ask.
  • The repository root has no package manager install step. Use repo wrappers at the root, and use package commands only inside verified package roots.
  • Inspect YAML through the managed wrapper lane, not ad hoc system Python: ./bin/ask repo yaml-inspect <repo-relative-yaml> --json --robot or mise run yaml-inspect -- <repo-relative-yaml>. Plain python3 is not a PyYAML contract for this repo.
  • Run Infrastructure Python tests through the locked Infrastructure environment, not the system Python from the repo root. Use bash Infrastructure/scripts/run-infrastructure-python.sh -m unittest tests.<module> or bash Infrastructure/scripts/run-infrastructure-python.sh -m pytest <path> so dependencies from Infrastructure/uv.lock are available.
  • Before changing skills, sync policy, runtime projections, or agent-facing docs, read UBIQUITOUS_LANGUAGE.md.
  • Before changing Skills SDK plans, specs, atlas visuals, capability claims, or product-direction docs, use the product-boundary terms in UBIQUITOUS_LANGUAGE.md: Foundry holds candidates awaiting SDK processing; SDK owns the agent-facing workflow, reusable tooling and required registry/runtime adapters. Tessl holds checked versions privately; only Jamie decides public release. Codex home runtimes consume those versions. OpenAI plugins and system skills are exempt by verified origin. Follow the six rules in Path Ownership Boundaries. An explicit owner decision—not holding, checking or installation—decides editable source authority.
  • For a package selecting skills-sdk.gold-standard.v1, read Skills SDK Authoring Contract, update references/contract.yaml: authoring_contract with the skill, and run ./bin/ask skills package verify <skill-path> --json --robot. That is a structural admission gate only: run the declared behavioral proof and the selected runtime or external lane before claiming the skill is ready.
  • Edit canonical sources, not runtime projections. See Path Ownership Boundaries.
  • Finish the named outcome through the smallest local change and focused proof. Feedback is diagnostic evidence, not automatic authority to stop delivery or add process. Select the High-Signal Steering Feedback only for its named conditions. Routine delivery does not require a steering ledger entry or new process artifact. When that route is selected, opening and reading it in the current turn is required; record the result in .harness/quality/steering-uptake.md and run python3 Infrastructure/scripts/validation-and-linting/validate_steering_uptake.py --json.
  • Keep runtime handles operation-bound: wait, poll, or resume only the latest valid handle returned for that operation, following the tool's lifecycle rules. Unrelated tool calls do not invalidate a live handle. Perform these operations serially for that handle. See High-Signal Steering Feedback for recovery rules.
  • Separation coordination: task 01a025cc-c335-71b2-89ba-e32d7b0bf848 is the master controller for OC - Skills SDK and OC - Foundry. It assigns bounded migration units and accepts their evidence; owners do not start product refinement or redefine programme completion. Use completion messages, not polling or periodic status loops. Follow PM Thread Coordination.
  • Keep local, runtime, cloud, Tessl, and release proof separate. Use Tessl Live Skill Eval Workflow and Skills SDK Runtime Lane Contract for the applicable selected actions. Registry and runtime proof remain required programme outcomes; a local task does not authorise live side effects.

Read the full file on GitHub · 112 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. 1mo ago Changed · +10 lines · +146 tokens per session d563906119bb
  2. 1mo ago Changed · +1 lines · +17 tokens per session 22a466b12828
  3. 1mo ago Changed · +5 lines · +78 tokens per session ec4d9345e0c6
  4. 1mo ago First seen · 96 lines · 1,271 tokens per session scan A a15750bbdfd4

Subscribe to this mod's changes

Agent-Skills AGENTS.md is an instructions file published in the GitHub repository jscraik/Agent-Skills (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,512 tokens to every session, about $0.0060 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-31.

agent-skillsagentic-workflowai-agentsautomationcodexdeveloper-tools
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 · 9,715 tokens

next.js AGENTS.md

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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

vscode model-prompts.instructions.md

Model-specific prompt authoring and registry guidelines.

microsoft/vscode · 2,022 tokens