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.
npx agentmods add rules/featurefactory-io/mimir/assert-log-storygit clone --depth 1 https://github.com/FeatureFactory-io/mimirWhat 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 | $0.00332 | $0.00332 |
| Opus 5 | $0.00166 | $0.00166 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
assert-log-story 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 2d 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.
What it actually says
Mimir metadata: slug do-assert-log-story; always_apply: false (link to BPE-02 / MIN-04 / TFK-02).
When a plan or iteration manifest declares a Log Story Script (or log_story_script[] / log_tests[]), you MUST prove those beats with pytest caplog (or equivalent log capture) — not by grepping logs/app.log alone, and not by “logging statements exist” checklists.
Requirements
- For each Log Story Script row, a test asserts the
where+beat+must_includefragments appear in captured logs at the declared level (default INFO; WARNING/ERROR when the script says so). - Cover happy and reject paths when the scenario has both (
test_*_log_story_happy/test_*_log_story_reject). - Use the shared helper from skill Pytest Log Story Assertions (
tests/support/log_story.py→assert_log_story(...)) once TFK-02 has bootstrapped it. - Log-story tests ship in the same commit as behavior green — never a deferred logging slice.
- Never assert on raw secrets, tokens, or passwords in log lines.
Anti-patterns
- Behavior test green while log story absent or weakened to
logger.info("done") - Manual
logs/app.loginspection as the only DoD for observability - Skipping
checkpoint.log_story_commandwhen the manifest listslog_tests
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.
- 2d ago First seen · 22 lines · 332 tokens per session scan A 8972fb91307a
assert-log-story is a cursor rule published in the GitHub repository FeatureFactory-io/mimir (13 stars, last pushed 4d ago), licensed Apache-2.0. It adds 332 tokens to every session, about $0.0017 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.