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/harnessprotocol/harness-kit/capturenpx skills add harnessprotocol/harness-kit --skill capturegit clone --depth 1 https://github.com/harnessprotocol/harness-kitWhat 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.00073 | $0.00997 |
| Opus 5 | $0.00036 | $0.00498 |
| Sonnet 5 | $0.00015 | $0.00199 |
| Haiku 4.5 | $0.00007 | $0.00100 |
Grade A, and why
capture 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Staging
Overview
Capture information from the current conversation into a staging file for the daily reflection pipeline to consume and write to the knowledge graph.
Core principles:
- Token-conscious — 3-8 bullets, max 20 words each
- Complementary to Stop hook — captures nuance and specificity the auto-summary misses
- Append-only — never modify existing entries in the staging file
- Confirm what was staged — always show the user exactly what was written
Argument Types
| Argument | Behavior |
|---|---|
| (none) | Auto-extract 3-8 most important facts from the conversation |
| Specific text | Stage the provided facts as bullets |
decisions |
Extract only decisions made this session |
technical |
Extract only technical facts and implementation details |
Workflow (MANDATORY — follow in order)
Step 1: Parse Input
Classify the argument:
- No argument → auto-extract mode
- Exactly the word
decisions→ filter to decisions only - Exactly the word
technical→ filter to technical facts only - Anything else → treat as specific facts provided by the user
Step 2: Resolve Staging File
Check in order:
scripts/session-staging.mdin the project root (current working directory)~/.claude/session-staging.mdas fallback
If the resolved file does not exist, create it with this header:
# Session Staging
Facts staged here are consumed by the daily reflection and written to the knowledge graph.
Step 3: Extract or Formulate Bullets
Based on argument type, produce 3-8 bullets. Each bullet: max 20 words, factual, specific.
Auto-extract (no argument): Scan the conversation for the most important facts — decisions made, technical details learned, status changes, new entities or tools introduced. Prefer concrete facts over vague summaries.
Specific facts (user-provided text): Convert the user's text into clean bullet points. If they already gave you bullets, clean and tighten them. If they gave you prose, extract the key facts.
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 · 105 lines · 73 tokens per session scan A ca96a94da504
capture is a skill published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 73 tokens to every session and 997 once invoked, about $0.0004 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-31.
Other skills, from other repositories
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.
epd-to-spec
Write CSI specification language for EPD submittals and sourced GWP limits. Use to add embodied-carbon or EPD requirements to specs; not to parse, find, or compare EPDs.
occupancy-calculator
Calculate code occupant loads by area with gross/net factors and jurisdiction checks. Use for "how many people can this space hold," IBC Table 1004.5, egress inputs, or occupancy-load reports; not for workplace headcount planning.
zoning-analysis-nyc
Analyze NYC lot zoning, FAR, height, setbacks, uses, and buildable envelope from PLUTO and the Zoning Resolution. Use for "what can I build"; use nyc-bsa for relief and zoning-envelope for 3D visualization.
workplace-programmer
Build office space programs through guided workplace strategy: area splits, room schedules, and planned seat counts. Use to program or size a workplace; not for code occupant-load calculations.
workplan
Create a durable, execution-ready work plan for repository changes, operations, research, or AEC project delivery. Use when the user asks to plan, scope, sequence, coordinate, or break down multi-step work before acting. Do not use for floor plans, site plans, space planning, zoning calculations, building-code…