agentmods.dev

capture-and-route

capture-and-route is a skill for Claude Code, Codex from regen-coordination/org-os-template. It costs 49 tokens per session (690 once invoked), scanned A, original, MIT.

An intake and sorting guide for turning a link, pasted text, transcript, repository, post, question, or observation into several typed records. It keeps track of the source, maturity, and whether each record is ready for public use.

In plain words
What is it for?
Use it to break reports and other inputs into resources, concepts, claims, evidence, options, implementation ideas, signals, and source records.
Why use it?
It helps prevent useful information from staying as an unstructured note and preserves where each piece came from.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 5repo 4d ago A scan 49 tokens original MIT

Good fit Use it to break reports and other inputs into resources, concepts, claims, evidence, options, implementation ideas, signals, and source records.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/regen-coordination/org-os-template/capture-and-route
View source ↗ regen-coordination/org-os-template regen-coordination.github.io
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.

Any agent
npx skills add regen-coordination/org-os-template --skill capture-and-route
Clone the repo
git clone --depth 1 https://github.com/regen-coordination/org-os-template

Made for: Claude Code, Codex.

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

agentmods badge for capture-and-route

README.md
[![agentmods](https://agentmods.dev/badge/skills/regen-coordination/org-os-template/capture-and-route/github.svg)](https://agentmods.dev/skills/regen-coordination/org-os-template/capture-and-route)
Your own site
<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/capture-and-route"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/capture-and-route/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.

agentmods 80×15 button for capture-and-route

Your own site · 80×15
<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/capture-and-route"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/capture-and-route.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 690 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00049 $0.00690
Opus 5 $0.00024 $0.00345
Sonnet 5 $0.00010 $0.00138
Haiku 4.5 $0.00005 $0.00069

Measured 10d ago against content hash b5fd9ab9706f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

capture-and-route 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 10d 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.

packages/toolkit-framework/skills/capture-and-route/SKILL.md · 39 lines

How it starts

The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.

capture-and-route

The contributor front door (master doc Principle 18 + §5 deep intake). A contributor adds one useful thing; the system routes it. Works in any agent context — no org-os required.

Core principle

Deep intake: one shared thing becomes many entries. A report can yield a Resource + Concepts + a Claim + Evidence + an Option-inspiration + an Implementation-candidate + a Signal + a Source-System part + a public-use-boundary case.

Inputs

Any of: a URL, pasted text, a call transcript, a GitHub repo, a tweet/thread, a forum post, a question, a pattern/failure observation.

Steps

  1. Identify the whole. What is this object as a whole? Where is it from? Who maintains it?
  2. Decompose (deep intake). Extract the candidate sub-objects, each typed via the kernel (schemas/kernel-profile.yaml → resource · concept · option · deployment · signal) or the full ontology (schemas/{core,extension}-entities.yaml).
  3. Source-system check. Is the origin a living knowledge environment (wiki/repo/forum/garden/podcast)? If so, draft a source-system card — and capture its return_path (the federation/reciprocity primitive). Source systems are peers, not link pools.
  4. Apply high-risk triggers. People/community profiles, exact locations, Indigenous/TEK knowledge, ecological/carbon/MRV claims, funding/legal/governance recommendations, identity/reputation → set high_risk: true and a public-use-boundary. Do NOT create public person-nodes by default. Retweets/mentions are signals, not endorsements.
  5. Assign state (K1, schemas/review-maturity.yaml). Set maturity, public_use, lifecycle_state honestly — a raw lead is raw / raw-lead, NOT reviewed. Mark ai_assisted: true for anything you synthesized.
  6. Route. Resource → Layer 3; Concept → Layer 2/4; Option → Layer 5; Deployment → Layer 6; Implementation → Layer 8; Signal → Layer 9. Leave a toolkit_route.
  7. Preserve provenance (schemas/provenance.yaml): origin, surfaced_by, transformation (quoted/summarized/synthesized/…), authorship.
  8. Validate each emitted object: toolkit-framework validate <schema> <file>.

Read the full file on GitHub · 39 lines

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. 10d ago First seen · 39 lines · 49 tokens per session scan A b5fd9ab9706f

Subscribe to this mod's changes

capture-and-route is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 690 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-31.

Research
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens