architect

A research-backed review of how a personal knowledge system could evolve, based on health reports, recurring difficulties, and its design history. It proposes changes but does not apply them automatically.

In plain words
What is it for?
Use it to assess a knowledge system or a specific area such as note processing, structure, or automation, then receive prioritized recommendations for improvement.
Why use it?
It turns observed friction and system problems into specific improvement proposals with supporting reasoning. Requiring approval keeps the system from changing unexpectedly.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/agenticnotetaking/arscontexta/architect
Any agent
npx skills add agenticnotetaking/arscontexta --skill architect
Clone the repo
git clone --depth 1 https://github.com/agenticnotetaking/arscontexta

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,646 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.05646
Opus 5 $0.00021 $0.02823
Sonnet 5 $0.00008 $0.01129
Haiku 4.5 $0.00004 $0.00565

Measured yesterday against content hash f1967f070ca8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

architect 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.

skills/architect/SKILL.md · 569 lines

How it starts

The opening of the file, as written. The whole thing — 569 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:

  1. ops/derivation-manifest.md — vocabulary mapping, platform hints

    • Use vocabulary.notes for the notes folder name
    • Use vocabulary.note / vocabulary.note_plural for note type references
    • Use vocabulary.topic_map / vocabulary.topic_map_plural for MOC references
    • Use vocabulary.inbox for the inbox folder name
    • Use vocabulary.cmd_reflect for connection-finding command name
    • Use vocabulary.cmd_reweave for backward-pass command name
    • Use vocabulary.cmd_verify for verification command name
    • Use vocabulary.architect for the command name in output
  2. ops/config.yaml — processing depth, pipeline chaining, automation settings

  3. ops/derivation.md — original derivation record (the design intent baseline)

If these files don't exist, use universal defaults and warn the user.


EXECUTE NOW

Target: $ARGUMENTS

Parse immediately:

  • If target names a specific area (e.g., "schema", "processing", "MOC structure"): focus analysis on that area
  • If target is empty: run full-system analysis across all dimensions
  • If target is --dry-run: run analysis but do not offer implementation

Execute these phases sequentially:

  1. Locate system files and detect platform
  2. Read derivation record for design intent
  3. Analyze health data (recent report or live check)
  4. Scan for friction patterns across operational surfaces
  5. Consult research to ground evidence in specific claims
  6. Generate 3-5 ranked recommendations with full evidence chains
  7. Present to user and implement on approval

START NOW. Reference below defines the seven-phase workflow.


Philosophy

Evidence beats intuition. Research beats habit.

Every rule in the context file was a hypothesis. Every skill workflow was a design choice. Hypotheses need testing against operational reality. This skill connects three evidence streams — health data, friction patterns, and research claims — to produce specific, actionable recommendations.

Read the full file on GitHub · 569 lines

Files

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.

Changes

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.

  1. yesterday First seen · 569 lines · 42 tokens per session scan A f1967f070ca8

Subscribe to this mod's changes

architect is a skill published in the GitHub repository agenticnotetaking/arscontexta (3,483 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 5,646 once invoked, about $0.0002 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.

Related

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…

ractive/hyalo · 102 tokens

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…

ractive/hyalo · 102 tokens

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…

ractive/hyalo · 177 tokens

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…

ractive/hyalo · 150 tokens

hyalo-tidy

../../../crates/hyalo-cli/templates/skill-hyalo-tidy.md.

ractive/hyalo · 0 tokens

hyalo

../../../crates/hyalo-cli/templates/skill-hyalo.md.

ractive/hyalo · 0 tokens