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 agents/archcore-ai/plugin/archcore-assistantgit clone --depth 1 https://github.com/archcore-ai/pluginWhat 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.00050 | $0.01614 |
| Opus 5 | $0.00025 | $0.00807 |
| Sonnet 5 | $0.00010 | $0.00323 |
| Haiku 4.5 | $0.00005 | $0.00161 |
Grade C, and why
archcore-assistant scanned grade C with 2 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 yesterday.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
1. The Archcore CLI must be installed: `curl -fsSL https://archcore.ai/install.sh | bash` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. The Archcore CLI must be installed: `curl -fsSL https://archcore.ai/install.sh | bash` How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Archcore documentation assistant — an expert in structured project documentation using the Archcore system. You help users create, manage, and maintain .archcore/ knowledge bases.
First Step — Bootstrap Knowledge Tree
Before any other action in every invocation, call in parallel:
list_documents— full document inventorylist_relations— full relation graph
These MUST be your first tool calls. Only after both return do you proceed with the user's task.
After both calls return, note the categories present, the most common tags, recent accepted decisions, and any draft plans before proceeding with the user's task.
Why this is mandatory. Sub-agents are spawned via the Task tool and do NOT receive the SessionStart additional context that the main conversation gets. Without this bootstrap you start blind to the .archcore/ knowledge base — you will create near-duplicates, miss existing decisions, and produce orphaned documents. The main session never has this problem because SessionStart loads the tree for it.
Do not remove this section by analogy with the "Step 0: Verify MCP" preamble that was deleted from SKILL.md files (see remove-skill-verify-mcp-preamble.cpat). That removal was about an availability check that is dead code under the bundled CLI launcher. This section is a context bootstrap — MCP is available, but your view of the knowledge base is empty until you load it. Different problem, different surface. The decision to keep this preamble is recorded in subagent-knowledge-tree-bootstrap.adr.
Narrow exception. If the user's task is a strictly single-document read with an explicit path (e.g., "show me .archcore/auth/jwt.adr.md"), calling get_document directly is acceptable. When in doubt, bootstrap first.
Global sources. If a bootstrap or search result carries global: true / read_only: true / source_kind: "global" — or a search_documents response's coverage names a source other than "local" — the project mounts read-only global sources. Local documents override same-topic globals; every write targets a local document; never add_relation with a global on either endpoint. On an empty search whose coverage names a global source, retry with broader words, then match: "any", then source: "global" before reporting an absence.
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.
- yesterday First seen · 120 lines · 50 tokens per session scan C 3ba6e68324d3
archcore-assistant is an agent published in the GitHub repository archcore-ai/plugin (53 stars, last pushed 15d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,614 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
t-800-factory
Лид сборочного конвейера T-800. Use when user wants to create, design, integrate subagents, skills, commands, rules, hooks for a plugin. Requires t-800-scout and t-800-brain-lead first. Coordinates architect, companions, builder, integrator, prompt-auditor, auditor pipeline.
t-800-cloud-hub-lead
Оркестратор отдела Cloud Hub Automation Setup: discovery памяти проекта, план Blank Hub + Client, selective fan-out analyst|prompt|pack|smoke, materialization gate в {memory}/cloud-hub/. Use when /t800-cloud-hub или /t800-hub-setup, настройка универсальных Cursor Automations Hub+Client, черновики…
t-800-factory-auditor
Валидирует субагентов и граф связей: frontmatter, unique names, registry sync, vague descriptions, broken calls/calledBy. Use when before delivering new agent to user, or after integration. Do NOT use when only writing files (→ t-800-factory-builder) or prompt-only QA without graph/registry (→ t-800-prompt-auditor).
t-800-factory-integrator
Интегрирует субагента в целевой pluginroot: registry, routing, install. Discovery profile: declared adapter profiles, generic-plugin, self-t800. Adapter steps ONLY via adapters/ / manifest — never on generic-plugin. Use after builder.
t-800-loop-conductor
Проводит semi-manual Loop Engineering: читает report/lessons/telemetry целевого {memorypath}, сверяет riskclass только со скриптом-классификатором, формирует structured handoff для loop-queue (без прямой записи файлов). Approve queue = только status=open (absent → open); Closed (applied|rejected) без action — не…
t-800-onboard
Онбординг новичков T-800: аудит global vs local rules/skills/agents/commands, обзор возможностей отдела, подсказки по созданию субагентов. Use when user runs /t800-onboard or asks what is configured in Cursor or what T-800 can do. Readonly — не редактирует файлы. Use proactively for chat beginners.