agentleFS
tomw1808tomw1808/flash-agents/AGENTS.md

flash-agents

AGENTS.md9 starsChanged yesterdayMITView on GitHub

A Claude Code plugin: an MCP server (packages/flash-mcp/) that hands tasks to DeepSeek Harness workers inside a dsh sandbox, on macOS, Linux and Windows. Plain Node ESM, no TypeScript, no dependencies, no build step. - packages/flash-mcp/lib/: index.js (CLI, MCP tool schemas and descriptions), service.js (calls, results, warnings, worker instructions), isolation.js (copies, slots, patches, apply, caches), jobs.js (background jobs), proctree.js (process-tree watcher), doctor.js, config.js, sdk.js, mcp.js. - packages/flash-mcp/test/ (unit tests, node --test), test-support/ (the stand-in Harness), scripts/verify-live.mjs (the live suite, needs…

  • 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,439 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 repository3 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. Very specific:

    Check: npm test from the repository root (all three suites).

    line 16
  2. Distinctive:

    No silent defaults, caps, prefixes or truncation unless the task asks for them.

    line 23
  3. Distinctive:

    Every defect fixed gets a test that fails before and passes after, through the real entry point.

    line 26
  4. Very specific:

    Do not edit version numbers.

    line 27

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

Working in flash-agents

A Claude Code plugin: an MCP server (packages/flash-mcp/) that hands tasks to DeepSeek Harness workers inside a dsh sandbox, on macOS, Linux and Windows. Plain Node ESM, no TypeScript, no dependencies, no build step.

  • packages/flash-mcp/lib/: index.js (CLI, MCP tool schemas and descriptions), service.js (calls, results, warnings, worker instructions), isolation.js (copies, slots, patches, apply, caches), jobs.js (background jobs), proctree.js (process-tree watcher), doctor.js, config.js, sdk.js, mcp.js.
  • packages/flash-mcp/test/ (unit tests, node --test), test-support/ (the stand-in Harness), scripts/verify-live.mjs (the live suite, needs Ollama; never run it in a task).
  • packages/dsh-flash-guard/ (the command guard, lib/ and test/), packages/dsh-subagent-flash/.
  • README.md, docs/design.md, skills/ are user-facing docs.

Check: npm test from the repository root (all three suites). Run a single file with node --test packages/flash-mcp/test/<file>. Every change ends with a full npm test; paste the summary lines.

Hard rules:

  • Tests never touch the real home directory, the real DSH_HOME, the real temp state base or the real data directory: use temp dirs and the idioms of the existing tests. Never run real icacls.
  • No silent defaults, caps, prefixes or truncation unless the task asks for them; every threshold is a named constant with a comment saying why.
  • Match the surrounding style and comment density; JSDoc on new functions like the neighbours.
  • Every defect fixed gets a test that fails before and passes after, through the real entry point.
  • Do not edit version numbers. Do not touch docs/handoff-disk-hygiene.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.