Ars Contexta is a Claude Code plugin that creates a personalized knowledge system from a conversation about how someone thinks and works, using connected Markdown files, note-processing skills, hooks, navigation maps, and templates. It is for people who want an owned, persistent second brain tailored to their domain. The catalogue entries are its generated skills, hooks, agent, and plugin workflow.
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 agenticnotetaking/arscontexta --skill tasksgit clone --depth 1 https://github.com/agenticnotetaking/arscontextaWrote 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/agenticnotetaking/arscontexta/tasks)<a href="https://agentmods.dev/skills/agenticnotetaking/arscontexta/tasks"><img src="https://agentmods.dev/badge/skills/agenticnotetaking/arscontexta/tasks/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/agenticnotetaking/arscontexta/tasks"><img src="https://agentmods.dev/badge/skills/agenticnotetaking/arscontexta/tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 8 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Rogue Agent · line 35 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00049 | $0.02803 |
| Opus 5.5 | $0.00020 | $0.01121 |
| Sonnet 5.5 | $0.00010 | $0.00561 |
| Haiku 4.5 | $0.00005 | $0.00280 |
Grade A, and why
tasks 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 1mo 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 — 403 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- Use
vocabulary.notesfor the notes folder name - Use
vocabulary.note/vocabulary.note_pluralfor note type references - Use
vocabulary.topic_mapfor MOC references - Use
vocabulary.cmd_reflect/vocabulary.cmd_reweave/vocabulary.cmd_verifyfor phase command names
- Use
-
ops/config.yaml— pipeline chaining mode, automation settings
If no derivation file exists, use universal terms.
EXECUTE NOW
Target: $ARGUMENTS
Parse the operation:
- No arguments or
status: show task stack + queue state (combined view) add [description]: add a task to the stackdone [task-number]: mark a task as completeddrop [task-number]: remove a task without completingreorder [number] [position]: move a task to a different position in the stackdiscoveries: show only the Discoveries section
START NOW. Execute the requested operation.
Philosophy
Two systems, one view.
The task stack (ops/tasks.md) and the pipeline queue (ops/queue/queue.yaml or ops/queue/queue.json) serve different purposes:
| System | Purpose | Managed By | Updated By |
|---|---|---|---|
| Task stack | Human priorities — what YOU want to work on | You (via /tasks) | Manual: /tasks add, /tasks done |
| Pipeline queue | Automated processing state — what the SYSTEM needs to process | Pipeline skills | Automatic: /reduce, /ralph, /reflect |
/tasks shows BOTH so you always have a unified view of all pending work. The task stack is your working memory. The pipeline queue is the system's working memory. Together they answer: "What should I do next?"
Operations
/tasks (or /tasks status)
Show both the human task stack and the automated queue.
Step 1: Read task stack
# Read ops/tasks.md
cat ops/tasks.md 2>/dev/null
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.
- 1mo ago First seen · 403 lines · 49 tokens per session scan A 7d80f3ea780c
tasks is a skill published in the GitHub repository agenticnotetaking/arscontexta (3,511 stars, last pushed 8mo ago), licensed MIT. It adds 49 tokens to every session and 2,803 once invoked, about $0.0002 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
workflow-orchestrator
Use when starting or resuming a cairnkit delivery workflow.
grooming
Shape ambiguous work into an agreed, executable plan. Use when the user asks to groom, scope, decompose, or prepare work before implementation.
grooming-evidence
Ground work grooming in existing product evidence. Use while shaping tasks from code, documentation, tracker state, and user feedback.
submission
This skill should be used when the user asks to "write a query letter", "query", "querying", "pitch", "blurb", "back cover copy", "jacket copy", "comp titles", "comparable titles", "synopsis for agents", "submit to agents", "submission tracker", "self-publishing description", "retailer description", "ready to query"…
Folio Tables
Work with Folio data tables (kind table) through foliotable MCP tools — schema-first, column types, filters, and typical schemas for a risk register, sprint plan, or backlog.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.