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/nextnpx skills add agenticnotetaking/arscontexta --skill nextgit 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.00050 | $0.04673 |
| Opus 5 | $0.00025 | $0.02337 |
| Sonnet 5 | $0.00010 | $0.00935 |
| Haiku 4.5 | $0.00005 | $0.00467 |
Grade A, and why
next 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 2d 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 — 408 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, domain context- Use
vocabulary.notesfor the notes folder name - Use
vocabulary.inboxfor the inbox folder name - Use
vocabulary.notefor the note type name in output - Use
vocabulary.topic_mapfor MOC references - Use
vocabulary.cmd_reducefor process/extract command - Use
vocabulary.cmd_reflectfor connection-finding command - Use
vocabulary.cmd_reweavefor backward-pass command - Use
vocabulary.rethinkfor rethink command name
- Use
-
ops/config.yaml— thresholds, processing preferencesself_evolution.observation_threshold(default: 10)self_evolution.tension_threshold(default: 5)
If these files don't exist, use universal defaults and generic command names.
EXECUTE NOW
INVARIANT: /next recommends, it does not execute. Present one recommendation with rationale. The user decides what to do. This prevents cognitive outsourcing where the system makes all work decisions and the user becomes a rubber stamp.
Execute these steps IN ORDER:
Step 1: Read Vocabulary
Read ops/derivation-manifest.md (or fall back to ops/derivation.md) for domain vocabulary mapping. All output must use domain-native terms. If neither file exists, use universal terms (notes, inbox, topic map, etc).
Step 2: Reconcile Maintenance Queue
Before collecting state, evaluate all maintenance conditions and reconcile the queue. This ensures maintenance tasks are current before the recommendation engine runs.
Read queue file (ops/queue/queue.json or ops/queue.yaml). If schema_version < 3, migrate:
- Add
maintenance_conditionssection with default thresholds - Add
priorityfield to existing tasks (default: "pipeline") - Set
schema_version: 3
For each condition in maintenance_conditions:
- Evaluate the condition:
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.
- 2d ago First seen · 408 lines · 50 tokens per session scan A 6a654614357c
next is a skill published in the GitHub repository agenticnotetaking/arscontexta (3,486 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 4,673 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.