agentleFS
QSOLKCBQSOLKCB/CLAUDE-SKILLS-AGI/AGENTS.md

CLAUDE-SKILLS-AGI

AGENTS.md1 starsChanged 11 days agoMITView on GitHub

Never modify docs/CSA-002/USER_SUPPLIED_CLAUDE_REVIEW.md, PROMPT_AS_DRAFTED.md or OBSERVATION.md to retroactively correct the historical response or pre-change finding. Keep every newly proposed skill attributed through docs/CSA-002/ADOPTION.json. Preserve Long Live The Queen byte-for-byte; no empty minimalism exception. The real implementation must remain deterministic and simulated, not execute instructions as privileged commands.

The file

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

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep runtime zero-dependency, offline-first and GitHub Pages compatible with relative paths.

    line 12
  2. Distinctive:

    Use reviewable PRs; no automatic merging or deployment claims without observing the actual result.

    line 14
  3. Very specific:

    Never modify docs/CSA-002/USER_SUPPLIED_CLAUDE_REVIEW.md, PROMPT_AS_DRAFTED.md or OBSERVATION.md to retroactively correct the historical …

    line 18
  4. Very specific:

    Run python3 -m unittest discover -s tests -v, then load tests/browser-smoke.html over local HTTP or GitHub Pages.

    line 21

≈ “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

Agent Operating Instructions — CLAUDE-SKILLS-AGI

Mission

Preserve the central satire: the presentation is enterprise-grade, the fake reasoning is deterministically reproducible, and each satirical micro-skill has exactly one non-empty line. Never imply that this project offers genuine AGI, consciousness, working safety overrides, or official Anthropic functionality.

Hard invariants

  1. Skills live at skills/<id>/SKILL.md. Each has exactly one non-empty line, with a final LF permitted. Do not add YAML frontmatter.
  2. data/skills.json must include exactly the same instruction for each ID. The Python standard-library test suite guards this.
  3. assets/engine.js is a pure, stateless deterministic function of prompt, selected skill, seed, engine version and static manifest. No clock, RNG, external inference, local storage, or network dependency for generating answers.
  4. Changes to response rules, text, normalization, or hashing require a version update and an explicit reproducibility note.
  5. Render user prompts and model output with DOM textContent, never innerHTML. Do not use eval or execute prompt content.
  6. Keep runtime zero-dependency, offline-first and GitHub Pages compatible with relative paths. No Node.js/npm, Docker, hosted APIs, analytics, external fonts or trackers.
  7. Preserve the MIT license and conspicuous independent parody disclosures.
  8. Use reviewable PRs; no automatic merging or deployment claims without observing the actual result.

CSA-002 evidence preservation

Never modify docs/CSA-002/USER_SUPPLIED_CLAUDE_REVIEW.md, PROMPT_AS_DRAFTED.md or OBSERVATION.md to retroactively correct the historical response or pre-change finding. Keep every newly proposed skill attributed through docs/CSA-002/ADOPTION.json. Preserve Long Live The Queen byte-for-byte; no empty minimalism exception. The real implementation must remain deterministic and simulated, not execute instructions as privileged commands.

Verification

Run python3 -m unittest discover -s tests -v, then load tests/browser-smoke.html over local HTTP or GitHub Pages. Record executed tests separately from inferred properties. Never invent benchmarks or AGI performance metrics.

Tone

Excessively formal corporate engineering language surrounding ridiculously mundane capabilities. The jokes live in the skill text and clearly fictional marketing; the threat model, tests and provenance remain precise.

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.