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/tutorialnpx skills add agenticnotetaking/arscontexta --skill tutorialgit 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.00055 | $0.04358 |
| Opus 5 | $0.00028 | $0.02179 |
| Sonnet 5 | $0.00011 | $0.00872 |
| Haiku 4.5 | $0.00006 | $0.00436 |
Grade A, and why
tutorial 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 — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runtime Configuration (Step 0 — before any processing)
Read these files to configure domain-specific behavior:
-
ops/derivation-manifest.md— vocabulary mapping, platform hints- Use
vocabulary.notesfor the notes folder name - Use
vocabulary.note/vocabulary.note_pluralfor note type references - Use
vocabulary.reducefor the extraction verb - Use
vocabulary.reflectfor the connection-finding verb - Use
vocabulary.topic_mapfor MOC references - Use
vocabulary.inboxfor the inbox folder name
- Use
-
ops/config.yaml— processing depth, domain context
If these files don't exist, use universal defaults.
EXECUTE NOW
Target: $ARGUMENTS
- If
ops/tutorial-state.yamlexists andcurrent_step<= 5: resume from saved step - If target is "reset": delete
ops/tutorial-state.yamland start fresh - If no state file exists: begin new tutorial with track selection
START NOW. Reference below defines the flow.
Resume Detection
Read ops/tutorial-state.yaml. If it exists and tutorial is incomplete, display:
--=={ ars contexta : tutorial }==--
Welcome back.
Track: [track] [step-progress] Step [N] of 5
Resuming where you left off...
Skip to the saved current_step. Do NOT re-ask for track. If current_step > 5, tutorial is complete — offer to reset.
Progress indicator format:
- Step 1 of 5:
[=> ] - Step 2 of 5:
[==> ] - Step 3 of 5:
[===> ] - Step 4 of 5:
[====> ] - Step 5 of 5:
[=====>]
Track Selection (new tutorial only)
Display header, then use AskUserQuestion:
--=={ ars contexta : tutorial }==--
Which track fits your work best?
(a) Researcher -- academic papers, domain
research, literature processing
(b) Manager -- meeting notes, strategy docs,
decision tracking
(c) Personal -- daily observations, goal
setting, reflective journaling
Wait for response. Map a/b/c to researcher/manager/personal.
Write initial state to ops/tutorial-state.yaml:
track: [researcher|manager|personal]
current_step: 1
completed_steps: []
started: [ISO 8601 UTC]
last_activity: [ISO 8601 UTC]
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 · 497 lines · 55 tokens per session scan A c52a82af362a
tutorial is a skill published in the GitHub repository agenticnotetaking/arscontexta (3,483 stars, last pushed 6mo ago), licensed MIT. It adds 55 tokens to every session and 4,358 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…
core
This skill should be used when the user says "capture memory", "save to memory", "remember this", or trigger phrases like: "I've decided", "let's use", "we're going with", "I learned", "turns out", "TIL", "discovered", "I'm stuck", "blocked by", "always use", "never do", "convention is". Also triggers on recall…
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…
search
This skill should be used when the user says "search memories", "find in memories", "grep mnemonic", "look for memory", "deep search", "synthesize knowledge", or asks questions like "what do we know about X". Provides progressive disclosure and enhanced iterative search with synthesis.