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/regen-coordination/org-os-template/register-sourcenpx skills add regen-coordination/org-os-template --skill register-sourcegit clone --depth 1 https://github.com/regen-coordination/org-os-templateWrote 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/regen-coordination/org-os-template/register-source)<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/register-source"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/register-source.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00058 | $0.00510 |
| Opus 5 | $0.00029 | $0.00255 |
| Sonnet 5 | $0.00012 | $0.00102 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
register-source 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 5d 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.
What it actually says
register-source
Every ingestion starts here. Content objects reference their source system; the card must exist BEFORE the content does.
Steps
- Identify the source system behind the artifact: the living environment (wiki, repo, podcast, forum, newsletter, dataset, convening…) — not the file. A PDF someone sent is not the source system; the community that maintains it is.
- Draft the card (
schemas/source-system.yaml— check thetypeenum): required:title,type,steward,return_path(the reciprocity primitive: how corrections/contributions flow BACK). Fill honestly:reuse_conditions(license/permission — if unknown, say unknown and sethigh_risk: true),how_to_credit,currentness,update_rhythm,url. - No return path? That's a finding, not a blank — write
return_path: "none known — flag to steward"and raise asignalcandidate proposing outreach. Extraction without reciprocity is the pattern this framework exists to break. - Born-rules apply:
maturity: raw,ai_assisted: true,provenancewithorigin(where YOU learned of this source). - Referencing discipline for everything ingested from this source:
claims become
claim-evidencecandidates citing the source card's slug — never naked assertions in prose fields. - Emit as a candidate in the current work order (or via capture-and-route
for a standalone registration), then validate:
node <framework>/src/cli.mjs validate source-system <file>.
In the pilots
Self-ingestion registers the toolkit site + the master doc as source systems; ReFi DAO registers its podcast + blog; ReFi BCN its knowledge commons. The federation triangle (design spec §6a) is these cards pointing at each other.
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.
- 5d ago First seen · 42 lines · 58 tokens per session scan A 0cdb30ad963e
register-source is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 5d ago), licensed MIT. It adds 58 tokens to every session and 510 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…