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/savagelysubtle/BIG-BRAIN-Memory-BankWrote 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/savagelysubtle/big-brain-memory-bank/210-artifact-management-system)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/210-artifact-management-system"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/210-artifact-management-system/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/210-artifact-management-system"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/210-artifact-management-system.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.06223 |
| Opus 5.5 | $0.00000 | $0.02489 |
| Sonnet 5.5 | $0.00000 | $0.01245 |
| Haiku 4.5 | $0.00000 | $0.00622 |
Grade A, and why
210-artifact-management-system 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 2mo 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 — 1,033 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: WHEN managing design artifacts APPLY structured processes for organization and preservation globs: ["/*.md", "/*.mdc"] alwaysApply: true
TL;DR: The Artifact Management System provides structured processes for organizing, storing, retrieving, and maintaining design artifacts throughout their lifecycle to ensure knowledge preservation.
1.0.0
1. **Design Documentation**
- Design briefs
- Design rationales
- Decision records
- Evaluation matrices
- Review reports
- Verification results
2. **Design Specifications**
- Architecture specifications
- Component designs
- Interface contracts
- Algorithm definitions
- Data models
- UI specifications
3. **Design Diagrams**
- Architecture diagrams
- Component models
- Sequence diagrams
- State models
- Entity-relationship diagrams
- UI wireframes
4. **Alternative Designs**
- Exploration artifacts
- Alternative approaches
- Trade-off analyses
- Comparative evaluations
- Historical alternatives
- Evolution paths
5. **Reference Materials**
- Design patterns
- Best practices
- Reusable components
- Style guides
- Conventions
- External references
These artifact types encompass the full range of design knowledge.
1. **Type-Based Classification**
- Documentation category
- Specification type
- Diagram format
- Alternative classification
- Reference category
2. **Scope-Based Classification**
- System-level artifacts
- Subsystem artifacts
- Component artifacts
- Interface artifacts
- Implementation artifacts
3. **Status-Based Classification**
- Draft artifacts
- In-review artifacts
- Approved artifacts
- Deprecated artifacts
- Historical artifacts
4. **Purpose-Based Classification**
- Exploratory artifacts
- Decision artifacts
- Implementation artifacts
- Verification artifacts
- Educational artifacts
5. **Relationship-Based Classification**
- Parent/child relationships
- Dependency relationships
- Derivation relationships
- Version relationships
- Cross-reference relationships
These classification dimensions enable flexible organization.
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.
- 2mo ago First seen · 1,033 lines · 0 tokens per session scan A 85029f035e3f
210-artifact-management-system is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,223 tokens. 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-31.
Other cursor rules, from other repositories
components
Component patterns and UI conventions.
tailwind
Tailwind CSS and styling conventions.
components
Rules for component usage - which component libraries are allowed (shadcn/ui, Aceternity, Kibo, Magic UI, etc.), reuse over recreation, table implementation standards, and component modularization for both new features and existing components.
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
chakra-ui---semantic-html-rendering
Rules for rendering Chakra UI components as meaningful HTML elements such as sections, headings, paragraphs, and links. Semantic HTML uses element names that describe the role of the content.
designer
Cursor rule "designer" from ulises-jeremias/agent-toolkit, covering designer, when invoked, design routing — canonical (do not run mechanically), figma subtree and delegate to skills.