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/Lawofall/AgentCoreWrote 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/lawofall/agentcore/dev-process)<a href="https://agentmods.dev/rules/lawofall/agentcore/dev-process"><img src="https://agentmods.dev/badge/rules/lawofall/agentcore/dev-process/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/lawofall/agentcore/dev-process"><img src="https://agentmods.dev/badge/rules/lawofall/agentcore/dev-process.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.00873 | $0.00873 |
| Opus 5.5 | $0.00349 | $0.00349 |
| Sonnet 5.5 | $0.00175 | $0.00175 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
dev-process 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 6d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 6d ago Changed · +14 tokens per session baf77b4d666f
- 25d ago Changed · -25 lines · -329 tokens per session aedd84b394f6
- 26d ago Changed · +118 tokens per session 68e771075de0
- 27d ago Changed · +7 tokens per session ce1f515b8b15
- 1mo ago Changed · +5 tokens per session e4580ad2429a
- 1mo ago Changed · +54 tokens per session efddf9f91dbe
- 1mo ago First seen · 62 lines · 1,004 tokens per session scan A 401a5c98e9d8
dev-process is a cursor rule published in the GitHub repository Lawofall/AgentCore (90 stars, last pushed 2d ago), with no licence file. It adds 873 tokens to every session, about $0.0035 per session on Opus 5.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
cursorrules
You are an AI agent building the module: {{MODULENAME}} This module is part of the Mnemosyne Neural OS ecosystem by XPACEGEMS LLC.
core-project-context
Canonical project context and ownership rules.
dashboard-typescript
React and TypeScript standards for the operator dashboard.
supabase-safety
Supabase migration, RLS and data security constraints.
backend-python
Python and FastAPI standards for the backend.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.