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 skills/agenticnotetaking/arscontexta/setupnpx skills add agenticnotetaking/arscontexta --skill setupgit clone --depth 1 https://github.com/agenticnotetaking/arscontextaWhat 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.00053 | $0.17156 |
| Opus 5 | $0.00026 | $0.08578 |
| Sonnet 5 | $0.00011 | $0.03431 |
| Haiku 4.5 | $0.00005 | $0.01716 |
Grade A, and why
setup 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 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.
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 — 1,714 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Ars Contexta derivation engine. You are about to create someone's cognitive architecture. This is the single most important interaction in the product. Get it right and they have a thinking partner for years. Get it wrong and they have a folder of templates they will abandon in a week.
The difference is derivation: understanding WHO this person is, WHAT they need, and WHY those needs map to specific architectural choices. You are not filling out a form. You are having a conversation that reveals a knowledge system.
Reference Files
Read these files to understand the methodology and available components. Read them BEFORE starting any phase.
Core references (always read):
${CLAUDE_PLUGIN_ROOT}/reference/kernel.yaml-- the 15 kernel primitives (with enforcement levels)${CLAUDE_PLUGIN_ROOT}/reference/interaction-constraints.md-- dimension coupling rules, hard/soft constraint checks${CLAUDE_PLUGIN_ROOT}/reference/failure-modes.md-- 10 failure modes with domain vulnerability matrix${CLAUDE_PLUGIN_ROOT}/reference/vocabulary-transforms.md-- domain-native vocabulary mappings (6 transformation levels)${CLAUDE_PLUGIN_ROOT}/reference/personality-layer.md-- personality derivation (4 dimensions, conflict resolution, artifact transformation)${CLAUDE_PLUGIN_ROOT}/reference/three-spaces.md-- three-space architecture (self/notes/ops separation rules)${CLAUDE_PLUGIN_ROOT}/reference/use-case-presets.md-- 3 presets with pre-validated configurations${CLAUDE_PLUGIN_ROOT}/reference/conversation-patterns.md-- 5 worked examples validating derivation heuristics
Generation references (read during Phase 5):
${CLAUDE_PLUGIN_ROOT}/generators/claude-md.md-- CLAUDE.md generation template${CLAUDE_PLUGIN_ROOT}/generators/features/*.md-- composable feature blocks for context file composition
PHASE 1: Platform Detection
Automated. No user interaction needed.
Verify Claude Code environment:
Check filesystem:
.claude/ directory exists -> platform = "claude-code"
Neither -> platform = "minimal"
Existing .md notes detected -> note for proposal (V1: acknowledge and proceed fresh)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 1,714 lines · 53 tokens per session scan A ed21662235da
setup is a skill published in the GitHub repository agenticnotetaking/arscontexta (3,483 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 17,156 once invoked, about $0.0003 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 skills, from other repositories
dogfood
Run a dogfooding session for hyalo — build from source, exercise the CLI against real knowledgebases (own KB, MDN, GitHub Docs, VS Code docs), find bugs, verify recent fixes, assess UX, measure performance, and write a structured report. Use this skill whenever the user says /dogfood, "dogfood", "run a dogfood…
release
Cut a hyalo release end-to-end — verify/bump the workspace version, rotate the changelog with hyalo itself, sync the winget fork, publish the GitHub release with curated + auto-generated notes, and watch the pipeline. Use this skill whenever the user wants to release a new hyalo version, cut/tag/publish vX.Y.Z, says…
review-rust
Perform critical Rust code reviews covering correctness, edition 2024 compliance, error handling, API design, async pitfalls, and dependency hygiene. ALWAYS use this skill when the user wants to review, audit, or critically evaluate Rust code — whether that's a PR diff, a specific crate or module, a cross-cutting…
security-audit
REQUIRED skill for any security-related request. Use this skill whenever the user wants to find anything dangerous, sensitive, or risky in their code, files, or repository. This includes but is not limited to: scanning for secrets/keys/tokens/credentials, checking dependencies for vulnerabilities, auditing destructive…
hyalo-tidy
../../../crates/hyalo-cli/templates/skill-hyalo-tidy.md.
hyalo
../../../crates/hyalo-cli/templates/skill-hyalo.md.