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 agents/npatten/clew/domaingit clone --depth 1 https://github.com/npatten/ClewWhat 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.00000 | $0.00301 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
domain 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.
What it actually says
Domain Docs
How engineering skills should consume this repo's domain documentation.
Layout
This is a single-context repo.
Before architecture, diagnosis, TDD, issue-writing, or PRD work, read:
CONTEXT.md— compact domain vocabulary for Clew.clew-spec.md— full living design source and authoritative product semantics.docs/adr/— architectural decision records, if this directory exists.
If ADRs do not exist, proceed silently. Do not suggest creating ADRs upfront unless a durable architectural decision has actually been made.
Source of truth
CONTEXT.mddefines preferred vocabulary and terms to avoid.clew-spec.mdremains authoritative for detailed behavior, data model, workflow, and open questions.- If
CONTEXT.mdandclew-spec.mddisagree, treat it as drift: flag it and ask before making a semantic change.
Use the glossary vocabulary
When output names a domain concept, use the terms from CONTEXT.md.
Examples:
- Say Increment, not issue or ticket.
- Say Task, not sub-issue.
- Say Path, not roadmap.
- Say Archive, not closed issues.
- Say Tag, not label, when referring to Clew frontmatter tags.
Multi-context repos
This repo is not multi-context. Do not look for CONTEXT-MAP.md unless the repository layout changes later.
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 · 38 lines · 0 tokens per session scan A 262d508f5a75
domain is an agent published in the GitHub repository npatten/Clew (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 301 tokens. 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-31.
Other agents, from other repositories
mcp-connection
Connect Claude Code or any MCP-compatible agent to your Projektor instance.
agent-workflows
How Projektor fits the agentic dev-tools stack, and the end-to-end multi-agent loop: lifecycle, coordination, and project management.
tool-catalog
Every MCP tool Projektor exposes, generated from source.
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
workflow-spec
The canonical agent workflow rules: definition of ready, state machine, human gates, WIP limits.
flow-metrics
Every metric getflowmetrics returns, what it measures, and how to read it.