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 skills add archcore-ai/plugin --skill documentgit 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/skills/archcore-ai/plugin/document)<a href="https://agentmods.dev/skills/archcore-ai/plugin/document"><img src="https://agentmods.dev/badge/skills/archcore-ai/plugin/document/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/skills/archcore-ai/plugin/document"><img src="https://agentmods.dev/badge/skills/archcore-ai/plugin/document.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 64 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00183 | $0.02726 |
| Opus 5.5 | $0.00073 | $0.01090 |
| Sonnet 5.5 | $0.00037 | $0.00545 |
| Haiku 4.5 | $0.00018 | $0.00273 |
Grade A, and why
document 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 29d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/archcore:document
Record the present state: a technical decision, existing code, or a supplied
research material. The first word of the arguments selects the mode; a gate
inside the mode's track selects the document type. Write affinity: knowledge
types; a filed research and the decision cascade's plan belong to vision.
The standard cascade can add a cpat (experience).
Command tense: /archcore:plan declares a future canon delta, /archcore:document
records the present state — including work that shipped without a plan — and
/archcore:review reconciles a past declared delta. Δ vocabulary:
skills/_shared/delta-routing.md.
Load skills/_shared/gate-contract.md and skills/_shared/elicitation-contract.md before executing any gate.
Modes
| Mode | Track and entry | Types the entry gate selects |
|---|---|---|
decision |
skills/_shared/tracks/decision.md, decision.classify |
adr, rfc; rule through the standard cascade; an existing rfc draft on the topic → decision.resolve, which records an adr on an accepted verdict |
code |
skills/_shared/tracks/describe.md, describe.read |
spec, doc, guide, scenario |
research |
skills/_shared/tracks/research.md, research.frame |
research, rnd by the closing test; one external material → evidence |
A document type name is not a mode. When the subject text names a type (skills/_shared/gate-contract.md,
Entry terms) that the mode's track produces, the selecting gate treats that type as settled and asks no
type question: document decision rfc for gRPC reaches the RFC branch. A leading
word that is not a mode is topic text and goes through classification (Step 3).
No mode produces a journey; an intended user path belongs to /archcore:plan.
When to use
- "We decided to go with microservices" — settled decision
- "Record the decision to use PostgreSQL"
- "Document why we chose JWT over sessions"
- "Make this our team standard for error handling"
- "Draft an RFC for switching from REST to gRPC"
- "Should we switch to Kubernetes?" — open proposal
- "We accepted the proposal — resolve the RFC" — proposal resolution
- "Document the auth module"
- "Capture how the payment system works"
- "Create reference docs for the config system" — reference material
- "Write a guide for the release process" — how-to instructions
document code scenario for checkout— a user flow with examples over an existing specdocument research <report>— file a ready investigationdocument research <material>— file one external material as evidence
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.
- 29d ago Changed · +29 lines · +59 tokens per session 431ee11ca47a
- 1mo ago Changed · +1 lines f4ba1ecfede4
- 1mo ago Changed · +20 lines · +19 tokens per session ece4c4b93f2a
- 1mo ago First seen · 131 lines · 105 tokens per session scan A efd584f731c8
document is a skill published in the GitHub repository archcore-ai/plugin (58 stars, last pushed 26d ago), licensed Apache-2.0. It adds 183 tokens to every session and 2,726 once invoked, about $0.0007 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 skills, from other repositories
writing-style
Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.
root-cause-investigator
Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology. Use when user reports errors, build failures, test failures, performance issues, integration problems, or any "it's not working" scenarios.
connect
Install the scoped Antigravity permission hook.
mirrord-operator
Help users install and configure the mirrord Operator for team/enterprise environments. Use when users ask about operator setup, Helm installation, cloud API key or license configuration, air-gapped/offline licensing, enabling features (queue splitting, DB branching, preview environments, multi-cluster), internal…
digest
Generate a structured vibe-learn learning digest of the current coding session from .vibe-learn/session-log.jsonl.
quiz
Check your understanding of the vibe-learn session — recall questions grounded in the session log, with results tracked across sessions in the knowledge ledger.