agentleFS
frankxaifrankxai/agentic-income-skills/AGENTS.md

agentic-income-skills

AGENTS.md5 starsChanged 45 days agoMITView on GitHub

This repo is part of the FrankX / Starlight / Arcanea agent estate. Summarize changed files, validation run, risks, and any follow-up needed.

  • 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 32,671 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 repository4 other files it gives its agents.

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Default health command: npm test && npm run income:validate -- examples/request-to-quote-desk/income-system.json

    line 9
  2. Distinctive:

    Read this file before making changes.

    line 14
  3. Distinctive:

    Keep edits scoped to the requested task.

    line 16
  4. Distinctive:

    Prefer existing repo conventions over new abstractions.

    line 17
  5. Distinctive:

    Run the health command before handoff when feasible.

    line 18
  6. Common:

    Do not publish secrets, private memory, credentials, or internal-only strategy.

    line 19
  7. Very specific:

    Keep the trust rules in README.md intact: default-deny authority, human-gated pricing/transfers/claims, no pooled funds, no autonomous …

    line 24

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

Repository Instructions

This repo is part of the FrankX / Starlight / Arcanea agent estate.

Classification

  • Repo: agentic-income-skills
  • Class: public MIT-licensed skills/schema marketplace — Outcome Pack contracts for principal-owned agents that perform paid work
  • Default health command: npm test && npm run income:validate -- examples/request-to-quote-desk/income-system.json
  • Remote: https://github.com/frankxai/agentic-income-skills.git

Agent Rules

  • Read this file before making changes.
  • Preserve existing user work and unrelated dirty files.
  • Keep edits scoped to the requested task.
  • Prefer existing repo conventions over new abstractions.
  • Run the health command before handoff when feasible.
  • Do not publish secrets, private memory, credentials, or internal-only strategy.

Class-Specific Guidance

  • Preserve the schema (schemas/income-system.v1.schema.json), skill frontmatter, and scaffold script (scripts/scaffold-income-system.mjs) contracts.
  • Keep the trust rules in README.md intact: default-deny authority, human-gated pricing/transfers/claims, no pooled funds, no autonomous investment execution.
  • Affiliate/passive-income automation belongs to agenticpassiveincome / affiliate-agent-skills, not here — the skills/affiliate-audit adjunct is legacy-compatible only; don't grow it.
  • Validate examples/request-to-quote-desk against the schema after any contract change.

Handoff

Summarize changed files, validation run, risks, and any follow-up needed.

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.