AGENTS.md@loreA

AGENTS.md@lore from specstoryai/getspecstory is an AGENTS.md file: the standing instructions coding agents read in that repo.

Install it, pinned
mdr add specstoryai/getspecstory/lore/AGENTS.md@git:20260611.4e38e7b

Pins git:20260611.4e38e7b in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 14 of 14 checks passed
Kind
AGENTS.md file
Repository
specstoryai/getspecstory
Path
lore/AGENTS.md
Versions recorded
1
Latest version
git:20260611.4e38e7b, committed Jun 11, 2026
Size
1,620 bytes
Repository stars
1,358
License
Apache-2.0

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Agent Rules for the Lore Repo

You are working ON the lore engine/skill, not running it. Read [CONTRIBUTING.md](CONTRIBUTING.md)
first; these are the rules that bite:

- **Zero dependencies, ever.** Plain Node only (`node:sqlite`, `node:fs`, `node:crypto`). If a
  change seems to need an npm package, stop and ask.
- **The engine is deterministic; the agent judges.** Parsing/counting/fingerprinting/rendering live
  in `scripts/` and must be byte-reproducible. Judgment (naming, themes, verification) belongs in
  SKILL.md's contract or the workflow scripts.
- **Fixtures are the spec.** Every parsing or rendering claim needs a fixture
  (should-flag/should-pass style). New provider formats use REAL bytes verified against
  specstory-cli's writers - never invented. Parser behavior changes bump `PARSER_VERSION` in
  `scripts/lib/db.mjs`.
- **The golden file is intentional.** If `fixtures/golden/forge-plan.md` fails, either your change
  is wrong or the layout change is deliberate - regenerate with `UPDATE_GOLDEN=1 npm test` and say
  so in the commit body.
- **Never weaken the output contract.** PASS-THROUGH markers, sentinels, and the named failure
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add specstoryai/getspecstory/lore/AGENTS.md@sha256:7b24d1a047b82943

The line at the top of this page pins the label git:20260611.4e38e7b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_rdh7wjturtg5yyti.svg)](https://markdownregistry.com/a/art_rdh7wjturtg5yyti)

4 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Jun 11, 2026.

versioncommittedcommitsizeaudit
git:20260611.4e38e7b latest2026-06-11 4e38e7b 1,620 BA view

Audit of the latest version

A  14 of 14 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Size between 200 bytes and 200 KB (1620 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

specstoryai/getspecstory · 1,358 stars · license Apache-2.0 · pushed 2026-10-22 · branch dev

API

GET https://markdownregistry.com/api/v1/artifacts/art_rdh7wjturtg5yyti
GET https://markdownregistry.com/api/v1/resolve?ref=specstoryai/getspecstory/lore/AGENTS.md
GET https://markdownregistry.com/api/v1/blob/7b24d1a047b82943a57b4d61d8adacd395b8142aea86256b40fa7f96fbf86a47

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: how to write a good AGENTS.md · AGENTS.md vs CLAUDE.md · which agent file does what.

More from specstoryai/getspecstory

CLAUDE.md@lore CLAUDE.md file
specstoryai/getspecstory · lore/CLAUDE.md
git:20260611.4e38e7b · audit B · 1,358 stars
lore SKILL.md skill
specstoryai/getspecstory · lore/SKILL.md · SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a…
v3.9.0 · audit A · 1,358 stars
CLAUDE.md@specstory-cli CLAUDE.md file
specstoryai/getspecstory · specstory-cli/CLAUDE.md
git:20261018.8d18138 · audit A · 1,358 stars
workthreads SKILL.md skill
specstoryai/getspecstory · workthreads/SKILL.md · SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent -…
v1.0.0 · audit A · 1,358 stars

Every file in specstoryai/getspecstory

Browse by kind, by grade A, or by owner.