as-skill: Instructions file for Codex

AGENTS.md

as-skill AGENTS.md is an instructions file for Codex, OpenCode from alexeyshishin/as-skill. It costs 3,578 tokens per session, scanned C, original, MIT.

A repository instruction guide explains how a multi-domain collection of rules, skills, and agents is organized. It also defines the default behavior for agents working in that repository.

In plain words
What is it for?
It is for orienting agents before they work in the repository and directing them to its structure and always-on rules.
Why use it?
Agents can otherwise miss required repository conventions, available domains, or instructions that apply to every task.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

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

Reuse

Borrowing it

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

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 as-skill AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/alexeyshishin/as-skill/agents-md.svg)](https://agentmods.dev/instructions/alexeyshishin/as-skill/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/alexeyshishin/as-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/alexeyshishin/as-skill/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,578 This file is loaded in full into every session.
When invoked 3,578 The same file — it is already loaded in full.
Security scan C 1 finding. 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.1 $0.03578 $0.03578
Opus 5 $0.01789 $0.01789
Sonnet 5 $0.00716 $0.00716
Haiku 4.5 $0.00358 $0.00358

Measured 6d ago against content hash 4c4f750674e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade C, and why

as-skill AGENTS.md scanned grade C with 1 finding 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 6d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

how this repo's own root `.claude/` stays live (`rm -rf .claude && ./as-skill
AGENTS.md · 224 lines

How it starts

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

AGENTS.md

This file is the entry point for any AI agent working with the skills in this repository. Read it in full before your first action.

What this repository is

A multi-domain collection of rules, skills, and agents for Claude Code. Each domain is a self-contained vertical (Obsidian PKB, Git workflow, DevOps/Kubernetes, content, a code dev-loop harness). The layout is uniform; the working contract is shared across domains.

Always-on skill

Always run with the caveman core skill (domains/core/skills/caveman/) active — ultra-compressed output, full technical accuracy kept. Don't wait for the user to ask for brevity; it's the default in this repo.

Architecture

as-skill/
└── domains/
    ├── <domain-name>/
    │   ├── manifest.yaml      ← name, description, requires_env, targets
    │   ├── rules/             ← durable domain rules (optional — not every domain has one)
    │   ├── skills/<name>/     ← atomic operations: SKILL.md + README.md
    │   ├── agents/            ← orchestrators
    │   └── hooks/             ← optional; only `code` has one today
    ├── code/
    ├── content/
    ├── core/
    ├── devops/
    ├── git/
    └── obsidian/

Each domains/<name>/manifest.yaml declares:

  • name, description — what the domain is
  • requires_env — environment variables the domain won't deploy without (e.g. OBSIDIAN_VAULT for obsidian)
  • targets — where rules/skills/agents land after install

Dependencies run top-down: an agent knows about a skill, a skill knows about a rule. Not the reverse — except in code (see below).

Exception — code: the /code-plan, /code-build, /code-review, /code-debug skills are orchestrators that spawn subagents (code-planner, code-skeptic, code-reviewer, code-debugger) and merge their output — skill → agent, inverted from every other domain. code also has no rules/ directory; instead its skills/agents read .memory-bank/index.md and swarm-report/<slug>-*.md inside whichever project they're running in.

Read the full file on GitHub · 224 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. 6d ago First seen · 224 lines · 3,578 tokens per session scan C 4c4f750674e1

Subscribe to this mod's changes

as-skill AGENTS.md is an instructions file published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 17d ago), licensed MIT. It adds 3,578 tokens to every session, about $0.0179 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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

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,296 tokens

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

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 · 6,785 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

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,469 tokens

spec-kit AGENTS.md

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,104 tokens