Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/robotaitai/project-bedrockWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/robotaitai/project-bedrock/history-backfill)<a href="https://agentmods.dev/rules/robotaitai/project-bedrock/history-backfill"><img src="https://agentmods.dev/badge/rules/robotaitai/project-bedrock/history-backfill.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.00632 |
| Opus 5 | $0.00009 | $0.00316 |
| Sonnet 5 | $0.00003 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
history-backfill scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
History Backfill
After bootstrapping memory on a project with existing history, backfill the memory tree from evidence before proceeding with steady-state work.
Apply this rule once per project. It is not needed on every session.
When to apply
Apply after memory-bootstrap when the project:
- Has a git history with more than ~10 commits
- Has existing documentation (README, CLAUDE.md, AGENTS.md,
.agent-project.yaml,agent-knowledge/) - Has existing task files (
tasks/todo.md,tasks/lessons.md) - Was previously worked on by another agent or developer
Do NOT apply on every session — only when onboarding or when memory is newly empty.
Steps (summary — full detail in skill)
- Read the
history-backfillskill. - Run
scripts/import-agent-history.sh .to collect raw evidence. - Read evidence files in priority order (docs first, then manifests/configs/tests/workflows, then git and sessions).
- Distill stable facts into memory branch notes (Current State section).
- Record any architectural decisions found in
decisions/. - Update
Memory/MEMORY.mdbranch summaries to reflect real content. - Leave Open Questions for anything evidence hints at but doesn't resolve.
Evidence sources (priority order)
agent-knowledge/Evidence/imports/existing-docs.txt— README, CLAUDE.md, AGENTS.md,.agent-project.yamlagent-knowledge/Evidence/raw/manifests.txt— authoritative for stackagent-knowledge/Evidence/raw/config-files.txt— strong signal for conventionsagent-knowledge/Evidence/raw/tests.txtandraw/ci-workflows.txt— verification and deploy signalagent-knowledge/Evidence/raw/structure.txt— actual architecture shapeagent-knowledge/Evidence/imports/tasks.txtandimports/session-files.txt— context and recurring work areasagent-knowledge/Evidence/raw/git-log-detail.txtandraw/git-log.txt— why and what changed over timeagent-knowledge/Evidence/imports/trace-index.txt— supporting traces only, never canonical truth
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 68 lines · 17 tokens per session scan A 465e7de2d9cf
history-backfill is a cursor rule published in the GitHub repository robotaitai/project-bedrock (45 stars, last pushed 18d ago), licensed MIT. It adds 17 tokens to every session and 632 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
second-brain
WikiTicket SDD rules for Cursor agents (Grok Bot coding host).
CURSOR.rules
A set of Cursor rules that acts as the entry point for Baton, a project handoff system for keeping work, memory, and Git history consistent across AI coding tools.
cursor
Lore protocol integration -- query decision context before modifying files, write enriched commits.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.