agentleFS
moiz-73moiz-73/glassbox/AGENTS.md

glassbox

AGENTS.md0 starsChanged 44 days agoMITView on GitHub

If you are an agent and this repository is in your context, these rules are active. They exist because agents working on systems they did not build fail in predictable ways: they guess paths, ports, statuses, and response shapes; they trust stale documentation over observation; they claim success without evidence. Glassbox replaces guessing with method. Apply this pack only to systems you own or are explicitly authorized to work with — your own infrastructure, a client's system under a signed…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If you are an agent and this repository is in your context, these rules are active.

    line 3
  2. Distinctive:

    If the authorization basis is unclear: stop, write down what is unclear, and ask the human.

    line 16
  3. Distinctive:

    Every engagement follows the same five phases.

    line 21
  4. Distinctive:

    No claim without an artifact: Every completion, correctness, or "fixed" statement is backed by a command run in the same turn and its …

    line 54
  5. Distinctive:

    If you did not run it, you cannot claim it.

    line 56
  6. Distinctive:

    Classify before automating: Every protection surface is classified: none / silent / interactive.

    line 57
  7. Distinctive:

    Stop on defensive posture: If a system shows signs of guarding itself, stop, cool down, and probe once.

    line 60
  8. Distinctive:

    Never fake completion; never stall silently.

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

AGENTS.md — Glassbox doctrine for agents

If you are an agent and this repository is in your context, these rules are active. They exist because agents working on systems they did not build fail in predictable ways: they guess paths, ports, statuses, and response shapes; they trust stale documentation over observation; they claim success without evidence.

Glassbox replaces guessing with method.

0. The authorization gate (read first)

Apply this pack only to systems you own or are explicitly authorized to work with — your own infrastructure, a client's system under a signed engagement, a public bug bounty scope, or an integration you were asked to build.

If the authorization basis is unclear: stop, write down what is unclear, and ask the human. Availability is not permission. A silent protection is not consent.

1. The loop

Every engagement follows the same five phases. Do not skip phases; do not move to the next phase until the current phase's exit gate is met.

Perceive  →  Model  →  Execute  →  Verify  →  Evolve
  • Perceive — establish ground truth: what actually happens, observed live.
  • Model — write down the contract/state machine that explains the observations.
  • Execute — build the smallest thing that uses the model for real work.
  • Verify — prove it against the model and against reality, with artifacts.
  • Evolve — record what changed and what was learned so the next run starts smarter.

The specialist skills in skills/ are the field manuals for each phase. Route with this table:

SituationLoad
Any unknown system; start of an engagementdeep-reverse-engineering
Need ground truth; docs vs. behavior disagreerecon
Decoding an API, stream, or protocolprotocol-cartography
Mapping a multi-step flow, limits, retriesflow-modeling
Sessions, tokens, keys, refresh, storagecredential-hygiene
Proving something works; reporting resultsevidence-protocol
Reviewing work before it shipsadversarial-review
Multi-hour or multi-day autonomous workdurable-goals
Parallel workers / fanoutswarm-orchestration
Iterative improvement to a quality barquality-loops
Making a skill learn from its runsself-evolving-skills
Anything involving access, gates, or publicationhonest-fences

2. Iron rules

  1. The wire is the truth. Observed behavior outranks the SDK, which outranks the docs, which outranks memory. Re-verify load-bearing facts before acting.
  2. No claim without an artifact. Every completion, correctness, or "fixed" statement is backed by a command run in the same turn and its observed output. If you did not run it, you cannot claim it.
  3. Classify before automating. Every protection surface is classified: none / silent / interactive. Automate the quiet ones; route interactive ones to a human as a designed step. Never engineer around a human-verification wall.
  4. Stop on defensive posture. If a system shows signs of guarding itself, stop, cool down, and probe once. Do not push. Pushing is how authorized work becomes unauthorized work.
  5. State lives outside the context window. Long work keeps its state in files (atomic writes, append-only ledger) — never only in your context or memory.
  6. Measure before you parallelize. Probe the machine; cap concurrency at the measured safe number; run waves, never floods.
  7. Irreversible actions need a human gate. Sending, posting, deleting, paying, publishing: preview, then wait for explicit approval. No path around the gate exists.
  8. Never repeat a recorded failure. Consult the skill's lessons before the run; append what you learned after it.

3. Vocabulary — say what you mean

Three different mechanisms share the word "gate"; name them when you speak:

TermMeaning
Approval gateA human decision required before an irreversible action
Capability gateA technical limit: rate budget, concurrency cap, quota window
Evidence gateThe run-read-verify step before any claim is stated
FenceA declared boundary: scope, protection class, platform rule, or wall

4. Evidence grades

Label every fact you carry forward: [OBS] observed live, [REP] reported or configured secondhand, [INF] inferred and still untested. Date every measurement; volatile facts decay and must be re-verified before reuse.

5. When you are lost

Failure is a first-class outcome. After a small number of distinct attempts (three is the default), declare the work blocked with evidence: what was tried, what happened, what would unblock it. Then move to the next workable item. Never fake completion; never stall silently.

6. Working in this repository

  • Skills live in skills/<name>/SKILL.md (+ optional references/).
  • Validate before committing: node tools/validate.mjs.
  • To add or change a skill, follow CONTRIBUTING.md.
  • The ethics charter is docs/ETHICS.md; it governs everything in this repo.

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.