agentleFS
trac3r00trac3r00/agent-skills/AGENTS.md

agent-skills

AGENTS.md0 starsChanged 3 months agoMITView on GitHub

Generated: 2026-08-26 Commit: 184b217 Branch: main

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    No network/credentials/LLM calls inside guard CLIs — offline and deterministic, always.

    line 46
  2. Very specific:

    Never overwrite user files in sync-type tools (skill-sync skip-exists.

    line 47
  3. Very specific:

    Don't hand-edit one manifest: .claude-plugin/marketplace.json, .claude-plugin/plugin.json, .codex-plugin/plugin.json move together.

    line 49

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

PROJECT KNOWLEDGE BASE

Generated: 2026-08-26 Commit: 184b217 Branch: main

OVERVIEW

61 agent skills (SKILL.md standard) in five families; 35 are script-backed stdlib-only Python CLIs with exit-code gates, 22 are instruction-only. Installable as a Claude Code / Codex plugin or used from a clone by any SKILL.md-reading agent.

STRUCTURE

agent-skills/
├── .claude-plugin/   # marketplace.json (catalog) + plugin.json (metadata), version-locked together
├── .codex-plugin/    # Codex manifest; skills path ./skills/, no version field
├── .agents/plugins/  # generic marketplace manifest
├── skills/<name>/    # SKILL.md [+ scripts/*.py] [+ references/] [+ LICENSE.txt]
└── tests/test_skills.py  # single test module for ALL skill CLIs + repo-wide frontmatter validation

WHERE TO LOOK

TaskLocationNotes
Add a skillskills/<name>/SKILL.mdfrontmatter contract in skills/AGENTS.md; validated by tests
Add CLI teststests/test_skills.pyscript const near CB..SH, use run() helper
Bump release.claude-plugin/*.json, .codex-plugin/plugin.jsonkeep versions + descriptions in sync across all three
Skill families / inventoryREADME.md tablesupdate when adding a skill; counts are asserted nowhere — keep honest
CI.github/workflows/tests.ymlpytest matrix 3.9/3.11/3.12 + 2 smoke tests

CODE MAP

SymbolTypeLocationRole
run(script,*args,stdin)helpertests/test_skills.py:19subprocess runner all CLI tests share
test_every_skill_has_valid_frontmattertesttests/test_skills.pyrepo-wide gate: name==dir, description present
discover()fnskills/skill-sync/scripts/skill_sync.pyprovider-root scan, priority dedupe
SCANNERSdictskills/session-handoff/scripts/session_handoff.pyper-client session store readers
PROVIDER_ROOTSconstskills/skill-sync/scripts/skill_sync.pypriority-ordered skill dirs per provider

CONVENTIONS

  • CLI contract (all 35 script-backed skills): argparse, positional input or - stdin, --json, gates are strict > comparisons; rc 0 ok / 1 gate breach / 2 usage-or-input error.
  • Stdlib-only; sole exception: context-budget optionally uses tiktoken (chars/4 fallback).
  • Frontmatter: name (== dirname), description, version, license (with upstream attribution), metadata.agentskills.tags.
  • Ported skills keep upstream LICENSE.txt in-dir and a license: frontmatter line naming the source repo.
  • De-brand ported content: harness-specific tools named only as examples with plain-text fallbacks.

ANTI-PATTERNS (THIS PROJECT)

  • No network/credentials/LLM calls inside guard CLIs — offline and deterministic, always.
  • Never overwrite user files in sync-type tools (skill-sync skip-exists; session-handoff is read-only).
  • Tool claims stay honest: claim-audit is NOT a fact-checker; skill-decay "never used" is a review prompt, not proof; gate-graph overlap is a candidate, not semantic equivalence.
  • Don't hand-edit one manifest: .claude-plugin/marketplace.json, .claude-plugin/plugin.json, .codex-plugin/plugin.json move together.

COMMANDS

uvx pytest tests/ -q                 # full suite (112 tests)
python3 skills/<s>/scripts/<s>.py --help

NOTES

  • skills/ultimate-browsing/engine/AGENTS.md documents the vendored fetch engine — leave it upstream-shaped.
  • macOS: session-handoff normalizes /tmp -> /private/tmp; cwd matching is target-or-child, never parent.
  • CI tests Python 3.9 while README floor is 3.9 too — keep them aligned when bumping.

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.