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 skills add jamesgray-ai/handsonai-plugins --skill scaffolding-registrygit clone --depth 1 https://github.com/jamesgray-ai/handsonai-pluginsWrote 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/jamesgray-ai/handsonai-plugins/scaffolding-registry)<a href="https://agentmods.dev/skills/jamesgray-ai/handsonai-plugins/scaffolding-registry"><img src="https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/scaffolding-registry/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.
<a href="https://agentmods.dev/skills/jamesgray-ai/handsonai-plugins/scaffolding-registry"><img src="https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/scaffolding-registry.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00134 | $0.02491 |
| Opus 5 | $0.00067 | $0.01246 |
| Sonnet 5 | $0.00027 | $0.00498 |
| Haiku 4.5 | $0.00013 | $0.00249 |
Grade A, and why
scaffolding-registry 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 11d 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.
Scaffolding Registry
Stand up a student's AI Registry as an OKF v0.2 knowledge bundle: a registry/ folder with a SCHEMA.md producer profile and concept nodes for their real business. This is the on-ramp — a ~30-minute guided interview that gets a first, real Workflow node written and linked, not a demo.
What this builds
<workspace or repo root>/
├── REGISTRY.md ← Tier 1 dashboard (derived, never hand-edited)
├── registry-dashboard.html ← Tier 2 dashboard (derived, optional)
├── registry/ ← the OKF v0.2 bundle
│ ├── SCHEMA.md ← producer profile (written by scaffolding-registry)
│ ├── index.md ← bundle root; frontmatter okf_version: "0.2"
│ ├── log.md ← migrations + schema changes only
│ ├── businesses/ lines-of-business/ functions/
│ ├── processes/ workflows/ notes/
│ │ (each typed directory has its own index.md)
├── outputs/<workflow>/ ← raw-source layer, unchanged (requirements,
│ design-spec, runs.md, generated artifacts;
│ event-facts live here, never in nodes)
├── sops/ process-guides/ ← unchanged homes; nodes link to them
The registry is the structured record every framework skill reads and writes — naming-workflows stubs a Workflow node in it, deconstruct fills in requirements, run flips status to in-production, and so on all the way through improve. registry/SCHEMA.md is the contract that makes that possible: it defines the six concept types (Business, LineOfBusiness, Process, Workflow, Note, Function), their required frontmatter, and the rules — enum values, link discipline, banned fields — that every skill's writes and every maintenance pass's lint checks agree on. Write it once per workspace, using references/schema-template.md verbatim; after that, the student's own copy is authoritative and every skill re-reads it before writing.
What ships with it
4 files 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.
- 11d ago First seen · 105 lines · 134 tokens per session scan A d1c6bacfed39
scaffolding-registry is a skill published in the GitHub repository jamesgray-ai/handsonai-plugins (8 stars, last pushed 1mo ago), licensed MIT. It adds 134 tokens to every session and 2,491 once invoked, about $0.0007 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.