agentleFS
loursCreatifloursCreatif/ours-stack/AGENTS.md

ours-stack

AGENTS.md1 starsChanged 4 months agoMITView on GitHub

Install: git clone … ours-stack && cd ours-stack && ./setup Skills live in subfolders (bear-hours/, etc.). ./setup exposes them through local compatibility links for supported runtimes. Every study uses the same layout: No proof.md in the default layout. A standalone proof draft file is created only when the user explicitly runs /proof-draft (future skill). Standalone deep research (no brief required): Ad-hoc outputs (pasted text or standalone, no existing study folder): Register on each brief.md write: bin/ours-stack-register-study. Backfill existing studies: ./setup…

  • 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,843 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 repository12 other files it gives its agents.

The file

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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every study uses the same layout:

    line 16
  2. Very specific:

    After /infographic in PROMPT mode, user pastes result back → re-run with attachment + image_edit if available

    line 120
  3. Distinctive:

    Before any public proof: strip copyrighted long quotes, personal data, unreleased work.

    line 134

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

ours-stack

Install: git clone … ours-stack && cd ours-stack && ./setup

Skills live in subfolders (bear-hours/, etc.). ./setup exposes them through local compatibility links for supported runtimes.

Ethos

  • Deep over wide — one narrow wedge, mastered
  • Dense over shallow — Feynman extraction, open questions, no summary theater
  • Explain over consume — every session tends toward something you can explain
  • Show your work — notes live in studies/<slug>/, traceable and revisitable

Artifact contract

Every study uses the same layout:

studies/<slug>/
├── brief.md        # /bear-hours
├── notes.md        # /dense-read (session trace — guided tranches + tes réponses)
├── council.md      # /council (optional)
├── dialogue/       # /dialogue (optional)
│   └── <persona>/
│       ├── persona.md
│       └── dialogue.md
├── research.md           # /deep-research (optional, when linked to study)
├── sources-index.md
├── report.html           # /layout-html (optional)
├── mind-map.json         # /mind-map (optional, editable)
├── mind-map.html         # /mind-map (optional)
├── visual-proof.spec.md  # /infographic (when run)
├── visual-proof.png      # /infographic (optional — image_gen)
├── visual-proof.alt.md   # /infographic (optional)
├── infographic-prompt.md # /infographic (optional — no image tool)
├── memory-palace.json    # /memory-palace (optional)
└── memory-palace.html    # /memory-palace (optional)

No proof.md in the default layout. A standalone proof draft file is created only when the user explicitly runs /proof-draft (future skill).

Standalone deep research (no brief required):

research/<slug>/
├── report.md             # /deep-research — synthesis
├── sources-index.md      # /deep-research — full screening log (150–250+ in literature-review mode)
├── report.html           # /layout-html — mise en page HTML (optional)
├── mind-map.json         # /mind-map (optional, editable)
├── mind-map.html         # /mind-map (optional)
├── visual-proof.*        # /infographic — same pattern as studies/
├── memory-palace.json    # /memory-palace (optional)
└── memory-palace.html    # /memory-palace (optional)

Ad-hoc outputs (pasted text or standalone, no existing study folder):

output/layout/<slug>/
├── article.html        # /layout-html
└── visual-proof.*      # /infographic (pasted text mode)

output/council/<slug>/
└── council.md          # /council

output/dialogue/<slug>/
├── persona.md
└── dialogue.md         # /dialogue

output/mind-map/<slug>/
├── map.json            # /mind-map
└── map.html            # /mind-map

output/dense-read/<slug>/
└── notes.md            # /dense-read (ad-hoc, no brief)

Cross-session memory

~/.ours-stack/
├── studies-index.jsonl   # registered studies (slug, path, title, wedge, repo)
└── learnings.jsonl       # durable insights across sessions

Register on each brief.md write: bin/ours-stack-register-study. Backfill existing studies: ./setup (or bin/ours-stack-backfill-index).

Slug rules

  • Lowercase letters, digits, hyphens only (transformer-attention, gstack-overview)
  • Derive from the topic title; ask before reusing an existing slug
  • One slug = one study thread; fork with suffix if scope diverges (gstack-skills-v2)

Skills

SkillWhen to use
/bear-hoursNew topic, "what should I learn?", scope unclear — optional scan via studies-index.jsonl, 5 framing questions (entry angle → wedge); ## Source material defaults to TBD — run /source-scout, confirm slug before reuse
/source-scoutBrief exists, ## Source material is TBD or thin — wedge-locked search; exactly 3 sources (article + YouTube + joker), anchor + core in brief; URLs opened in browser
/dense-readAnchor + brief — lecture guidée tranche par tranche (3–6), une question par tranche, notes.md = trace avec tes réponses ; « lis tout seul » = mode extraction solo ; handoff → /mind-map
/deep-researchStandalone — classic funnel: 150–250+ sources discovered & screened (default), 15–25 read in depth, synthesis report + sources-index.md. No brief required
/layout-htmlFinished text → self-contained HTML (editorial typography, 3–7 inline SVG figures quoted from source) — report.md, notes, any .md/.txt, pasted text; opens offline; fidelity over beauty; no new research
/mind-mapInteractive mind map from brief/notes/report — mind-map.json (editable) + mind-map.html (pan/zoom, expand/collapse, source links); no new research
/memory-palaceOblique relief map (method of loci) — click buildings, drill-down interiors, concept panel; memory-palace.json + .html; no FPS movement
/infographicOne memorable visual from existing study/research text — image_gen when available, else export prompt (/visual-proof alias)
/councilTable ronde vivante — 3–5 historical/relevant figures debate a topic live in chat, the user participates at the table; meeting minutes in council.md
/dialogue1-on-1 Socratic dialogue with a historical/public figure — persona card + transcript; challenges beliefs; informed epistemic mode default (alias /dialogue-historique)
/study-statusRead-only dashboard — criteria checked, artifacts on disk, suggested next step per study; local studies/ + optional ~/.ours-stack/studies-index.jsonl; no file writes

Routing

  • User shares a learning goal without a plan → /bear-hours
  • User shares paper/chapter/URL without a brief → /bear-hours first
  • Brief exists, sources missing or "TBD" → /source-scout
  • User wants depth + summary on a topic (not framed as a study wedge) → /deep-research — not auto-chained from other skills
  • User wants HTML layout / infographics on any text or after deep research → /layout-html — not auto-chained
  • User wants mind map / carte mentale / hierarchical overview → /mind-map — not auto-chained; complement to /layout-html
  • User wants spatial memory / relief map / palais cliquable (not FPS) → /memory-palace — not auto-chained
  • User wants one shareable visual summary (poster, thread hook, slide) from notes/report/brief → /infographic (alias /visual-proof) — not auto-chained
  • After /infographic in PROMPT mode, user pastes result back → re-run with attachment + image_edit if available
  • User wants a round table, a debate between several figures ("fais discuter X, Y et Z", "table ronde", "réunion"), or /council → /council — not auto-chained
  • brief.md exists and user asks "what should I do next?" → /study-status for facts; /council only if the user wants to debate the question with a panel
  • User wants sources only → /source-scout, not /council
  • User wants full research answer → /deep-research, not /council
  • User wants 1-on-1 dialogue with a figure (Darwin, Tesla, …), "discuter avec", belief testing in character → /dialogue — not auto-chained
  • User wants several figures at once (round table, debate) → /council, not /dialogue
  • User has anchor source and wants dense extraction → /dense-read — not auto-chained
  • Brief exists, sources listed, user wants to read anchor against wedge → /dense-read (after /source-scout if sources TBD)
  • User has a brief and explicitly wants to publish → future /proof-draft (never auto-create proof.md)
  • User asks where studies stand, "où j'en suis", statut, tableau de bord, or "what's next" (status view) → /study-status — not auto-chained; use /council when the user wants a live panel debate, not a dashboard

Privacy

Before any public proof: strip copyrighted long quotes, personal data, unreleased work. Summarize in your own words.

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.