agentleFS
Sign inStart free
nagisanzeninnagisanzenin/modal-skill/CLAUDE.md

modal-skill

CLAUDE.md0 starsChanged 44 days agoMITView on GitHub

This repo ships one Agent Skill, skills/modal/, with thin per-platform manifests (.claude-plugin/, .codex-plugin/, .agents/plugins/, root plugin.json), following https://github.com/nagisanzenin/omniplugin. - The skill folder is the portable core and must stay self-contained: SKILL.md, references/, scripts/. Never make it depend on files outside skills/modal/. - Scripts stay stdlib-only. Run python3 skills/modal/scripts/selftest.py before every commit. - Every rule needs a receipt: a new lesson goes into references/lessons.md as symptom → cause → fix, with the date. - Modal facts are dated (client 1.5.5, 2026-09-30).…

  • In this repositoryOne other file it gives its agents.

The file

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

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Every rule needs a receipt: a new lesson goes into references/lessons.md as symptom → cause → fix, with the date.

    line 9
  2. Distinctive:

    Before adding a root-level file or directory, check which platforms scan that name (omniplugin rule R9).

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md

modal-skill: maintainer notes

This repo ships one Agent Skill, skills/modal/, with thin per-platform manifests (.claude-plugin/, .codex-plugin/, .agents/plugins/, root plugin.json), following https://github.com/nagisanzenin/omniplugin.

  • The skill folder is the portable core and must stay self-contained: SKILL.md, references/, scripts/. Never make it depend on files outside skills/modal/.
  • Scripts stay stdlib-only. Run python3 skills/modal/scripts/selftest.py before every commit.
  • Every rule needs a receipt: a new lesson goes into references/lessons.md as symptom → cause → fix, with the date.
  • Modal facts are dated (client 1.5.5, 2026-09-30). When you touch one, re-check it against modal --help or modal.com/docs and update the date in README "Scope".
  • Release: bump version in .claude-plugin/plugin.json and .codex-plugin/plugin.json together, update README honest status, tag vX.Y.Z.
  • Before adding a root-level file or directory, check which platforms scan that name (omniplugin rule R9).

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.

Check your setup, free