agentleFS
VECTORG99VECTORG99/acf/AGENTS.md

acf

AGENTS.md2 starsChanged 3 months agoMITView on GitHub

Canonical workflow for every agent using ACF to craft issues and PRs. Read this file top-to-bottom before using the skill.

  • Commits and pushes
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository10 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Head+tail preservation: keep the original request (head, max 500 tokens) and the most recent phase output (tail, max 1000 tokens) verbatim.

    line 106
  2. Very specific:

    Use install.sh to install ACF into any project.

    line 143
  3. Distinctive:

    If you prefer to copy files manually:

    line 168
  4. Very specific:

    Run the label creation commands from skills/06-label-metadata/SKILL.md in the target repo to create all canonical labels.

    line 185

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

ACF — AI Agent Directives

Canonical workflow for every agent using ACF to craft issues and PRs. Read this file top-to-bottom before using the skill.

Reading Order

  1. AGENTS.md (this file) — Agent workflow and conventions
  2. docs/ARCHITECTURE.md — Skill architecture and data flow
  3. docs/FLOW.md — End-to-end pipeline diagram
  4. docs/IDEAS.md — Source conversation and idea mapping
  5. docs/PROCESS.md — Build process and decision log
  6. docs/COMPACTION.md — Context compaction research (Kimi CLI) and caveman mode
  7. docs/COMPATIBILITY.md — Multi-agent compatibility (agentskills.io spec)
  8. docs/ROADMAP.md — Product roadmap and maturity assessment
  9. skills/acf/SKILL.md — Orchestrator skill (source of truth, mirrored at .devin/skills/acf/)
  10. skills/01-context-load/SKILL.md — Phase 1: context loading (mirrored at .devin/skills/01-context-load/)
  11. skills/02-stack-audit/SKILL.md — Phase 2: stack auditing (mirrored at .devin/skills/02-stack-audit/)
  12. skills/03-issue-craft/SKILL.md — Phase 3: issue crafting (mirrored at .devin/skills/03-issue-craft/)
  13. skills/04-pr-context/SKILL.md — Phase 4: PR context building (mirrored at .devin/skills/04-pr-context/)
  14. skills/05-frontend-preview/SKILL.md — Phase 5: frontend preview (optional) (mirrored at .devin/skills/05-frontend-preview/)
  15. skills/06-label-metadata/SKILL.md — Label taxonomy (mirrored at .devin/skills/06-label-metadata/)
  16. skills/07-compaction/SKILL.md — Phase 7: context compaction (mirrored at .devin/skills/07-compaction/)
  17. skills/08-caveman/SKILL.md — Phase 8: extreme compression (mirrored at .devin/skills/08-caveman/)
  18. skills/09-graph-scope/SKILL.md — Phase 0: dependency graph + blast radius (mirrored at .devin/skills/09-graph-scope/)
  19. templates/issue-contextualized.md — Issue body template
  20. templates/pr-contextualized.md — PR body template
  21. SECURITY.md — Security policy
  22. CONTRIBUTING.md — Contributing guidelines

Project Snapshot

MetricValue
Orchestrator skill1 (acf)
Sub-skills9 (context-load, stack-audit, issue-craft, pr-context, frontend-preview, label-metadata, compaction, caveman, graph-scope)
Templates2 (issue, PR)
Docs7 (ARCHITECTURE, FLOW, IDEAS, PROCESS, COMPACTION, COMPATIBILITY, ROADMAP)
Skill formatAgent Skills spec (agentskills.io) — compatible with Claude Code, Cursor, Codex CLI, OpenCode, OpenClaw, Devin
Source of truthskills/ (portable) + .devin/skills/ (Devin mirror)
Installerinstall.sh — auto-detect, --all, --agent <name>
Dependenciesgh CLI, optional: Playwright (frontend-preview)
CompactionKimi CLI-inspired (phase 7) + caveman extreme mode (phase 8)
SecuritySECURITY.md, CODEOWNERS, CI secret scan, skill validation CI
Tests7 suites (validate, install, integration, compatibility, benchmark, MCP, Playwright) — 69 script + 95 behavior + 36 MCP + 13 Playwright = 213 total, all passing

Preferred Workflow

┌─────────────────────────────────────────────────────────────────┐
│  0. GRAPH-SCOPE   →  Decompose project into dependency graph,    │
│                      compute affected subgraph (large projects)  │
│  1. CONTEXT-LOAD  →  Read project MDs + scoped files, build      │
│                      snapshot                                    │
│  2. STACK-AUDIT   →  Detect orphan PRs, stale issues, libs       │
│  3. ISSUE-CRAFT   →  Craft issue with AC, labels, metadata       │
│  4. PR-CONTEXT    →  Build PR body with issue context            │
│  5. FRONTEND-PREVIEW (optional) → Visual diff, screenshot        │
│  6. LAUNCH        →  gh issue create / gh pr create              │
│  7. COMPACTION (auto/optional) → Kimi-inspired context compaction│
│  8. CAVEMAN (optional, extreme) → <500 tokens extreme compression│
└─────────────────────────────────────────────────────────────────┘

Phases 7 and 8 can trigger at any point after context-load when the accumulated context exceeds the token budget.

Phase Rules

  • Never skip context-load — every issue and PR must be built from a snapshot
  • Never skip stack-audit — always check for orphan PRs and escaped issues
  • Max 2 AC for autonomous issues — more than 2 = decompose or batch-delivery
  • Library suggestions are separate issues — never bundle into the main issue
  • Labels are mandatory — type + priority + area, minimum 3 labels per issue
  • Context is compressed — reference paths, never inline file contents
  • Compaction triggers at ~2000 tokens — auto-compact using Kimi techniques
  • Caveman triggers when compaction is not enough — target <500 tokens

Context Compression Rules

ACF has three compression tiers:

TierPhaseTarget tokensWhen to use
Full1-6~2000Default, large context window
Compacted7~800Standard compression (Kimi-inspired)
Caveman8<500Extreme, small context window or budget

Compression principles (all tiers)

  1. Paths, not contents — src/shared/Constants.luau not the file's code
  2. Commands, not configs — lune run scripts/test_core.luau not the test file
  3. Check names, not YAML — test (lune) not the full workflow
  4. Counts, not lists — "26 services" not all 26 service names
  5. Labels, not body text — priority:P1 not "Priority: High" in body
  6. Max 5 bullets per section in the snapshot

Compaction-specific (phase 7)

  • Head+tail preservation: keep the original request (head, max 500 tokens) and the most recent phase output (tail, max 1000 tokens) verbatim; compact the middle
  • Priority-based: preserve task state, errors, test commands, CI checks
  • XML-tagged output: <current_focus>, <stack>, <tests>, <ci>
  • First-person handoff: progress file reads as agent's own working notes

Caveman-specific (phase 8)

  • No prose — only paths, commands, labels, numbers
  • Symbols over words — →, |, #N
  • Bare caveman last resort — only NOW + NEXT + TESTS + CI (~100 tokens)

See docs/COMPACTION.md for the full research and design notes.


Label Taxonomy (summary)

See skills/06-label-metadata/SKILL.md for full taxonomy.

CategoryLabels
Typebug, enhancement, documentation, refactor, chore, test, security
Prioritypriority:P0, priority:P1, priority:P2, priority:P3
Areaarea:backend, area:frontend, area:ci, area:docs, area:security, area:devops
Statusready-to-implement, needs-metadata, blocked, needs-human
Enhancementlibrary-review, batch-delivery

Every issue MUST have: 1 type + 1 priority + 1 area label (minimum).


Installation

Universal installer (recommended)

Use install.sh to install ACF into any project. It auto-detects which agent directories exist and installs to all of them:

./install.sh /target/project

Install to ALL supported agents (creating directories as needed):

./install.sh /target/project --all

Install to a specific agent only:

./install.sh /target/project --agent claude

Supported agents: devin, claude, cursor, codex, agents, opencode

See docs/COMPATIBILITY.md for the full compatibility matrix.

Manual installation

If you prefer to copy files manually:

Devin:

cp -r .devin/skills/* /target/project/.devin/skills/

Claude Code / Cursor / Codex / OpenCode / OpenClaw:

cp -r skills/* /target/project/.claude/skills/

(Replace .claude/skills/ with the appropriate path for your agent — see docs/COMPATIBILITY.md for the path table.)

Label setup

Run the label creation commands from skills/06-label-metadata/SKILL.md in the target repo to create all canonical labels.


Git Commits

feat:     New skill phase or feature
fix:      Bug fix in a skill
docs:     Documentation change
refactor: Skill reorganization
chore:    Build, config, tooling

Key File Reference

PurposeFile (portable)Devin mirror
Orchestrator skillskills/acf/SKILL.md.devin/skills/acf/SKILL.md
Phase 1: context-loadskills/01-context-load/SKILL.md.devin/skills/01-context-load/SKILL.md
Phase 2: stack-auditskills/02-stack-audit/SKILL.md.devin/skills/02-stack-audit/SKILL.md
Phase 3: issue-craftskills/03-issue-craft/SKILL.md.devin/skills/03-issue-craft/SKILL.md
Phase 4: pr-contextskills/04-pr-context/SKILL.md.devin/skills/04-pr-context/SKILL.md
Phase 5: frontend-previewskills/05-frontend-preview/SKILL.md.devin/skills/05-frontend-preview/SKILL.md
Phase 6: label-metadataskills/06-label-metadata/SKILL.md.devin/skills/06-label-metadata/SKILL.md
Phase 7: compactionskills/07-compaction/SKILL.md.devin/skills/07-compaction/SKILL.md
Phase 8: cavemanskills/08-caveman/SKILL.md.devin/skills/08-caveman/SKILL.md
Phase 0: graph-scopeskills/09-graph-scope/SKILL.md.devin/skills/09-graph-scope/SKILL.md
Issue templatetemplates/issue-contextualized.md—
PR templatetemplates/pr-contextualized.md—
Architecturedocs/ARCHITECTURE.md—
Flow diagramdocs/FLOW.md—
Ideas mappingdocs/IDEAS.md—
Build processdocs/PROCESS.md—
Compaction researchdocs/COMPACTION.md—
Multi-agent compatibilitydocs/COMPATIBILITY.md—
Roadmapdocs/ROADMAP.md—
Installerinstall.sh—
Skill validatorscripts/validate-skills.sh—
Validator testsscripts/test-validate.sh—
Installer testsscripts/test-install.sh—
Integration testsscripts/test-integration.sh—
Compaction benchmarkscripts/benchmark-compaction.sh—
Full test runnerscripts/test-all.sh—
Security policySECURITY.md—
Contributing guideCONTRIBUTING.md—
Code of conductCODE_OF_CONDUCT.md—

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.