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/archcore-ai/pluginWrote 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/archcore-ai/plugin/archcore-context)<a href="https://agentmods.dev/rules/archcore-ai/plugin/archcore-context"><img src="https://agentmods.dev/badge/rules/archcore-ai/plugin/archcore-context/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/archcore-ai/plugin/archcore-context"><img src="https://agentmods.dev/badge/rules/archcore-ai/plugin/archcore-context.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.00234 | $0.00234 |
| Opus 5.5 | $0.00094 | $0.00094 |
| Sonnet 5.5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
archcore-context 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 1mo 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
Archcore — Git-native context for AI coding agents
You have Archcore MCP tools available for managing the .archcore/ knowledge base.
MCP Tools
list_documents— query documents by type, status, category, tagsget_document— read full content + metadata + relationscreate_document— create new document with validation and templatingupdate_document— modify existing documentremove_document— delete document and clean up relationsadd_relation— link two documents (related, implements, extends, depends_on)remove_relation— unlink documentslist_relations— query the relation graph
Critical Rule
All .archcore/ document operations MUST go through MCP tools. Never write directly to .archcore/*.md files — use create_document, update_document, or remove_document instead. This ensures validation, templates, and the sync manifest stay consistent.
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.
- 1mo ago First seen · 24 lines · 234 tokens per session scan A 5d2b5eab40e4
archcore-context is a cursor rule published in the GitHub repository archcore-ai/plugin (58 stars, last pushed 25d ago), licensed Apache-2.0. It adds 234 tokens to every session, about $0.0009 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
digital-brain
A Claude Code plugin and Obsidian vault that builds persistent, compounding knowledge bases using Andrej Karpathy's LLM Wiki pattern. This repo works with Cursor's AI through the cross-platform Agent Skills format.
search-routing
Smart Search Routing — always use QMD semantic search when available, never bypass with grep for vault content.
decision-logger
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting…
context-discipline
Manage AI context window efficiently - read before write, no re-reads, tool-call budgets, one-pass discipline.
context-management
Context window management — prevents AI from losing track during long sessions.
pn-plugin-quality-gates
Keep Cursor plugin manifests, paths, and component metadata valid during plugin authoring.