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 shawnclybor/clybor-claude-tooling --skill graduate-projectgit clone --depth 1 https://github.com/shawnclybor/clybor-claude-toolingWrote 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/shawnclybor/clybor-claude-tooling/graduate-project)<a href="https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/graduate-project"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/graduate-project/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/shawnclybor/clybor-claude-tooling/graduate-project"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/graduate-project.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.00143 | $0.01065 |
| Opus 5.5 | $0.00057 | $0.00426 |
| Sonnet 5.5 | $0.00029 | $0.00213 |
| Haiku 4.5 | $0.00014 | $0.00106 |
Grade A, and why
graduate-project 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 1mo 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
graduate-project
Turns a life-crm project folder into a graduated ~/gits/<slug> repo and connects the two via the OKF spine (Clybor OKF profile — ~/gits/life-crm/docs/okf-profile.md). The Notion Project ID is the join key; check-spine.py keeps the link honest. Six steps, one at a time. Confirm the destination before scaffolding; never mutate a NEW repo without the user's OK.
Step 0 — Read the registry row (source of truth)
Read ~/gits/life-crm/docs/project-registry.md for the project's section: Notion Project ID, Local folder, existing Related repos. If the project isn't in the registry, STOP and ask — graduation assumes a signed/active project. Never guess the Notion ID.
Step 1 — Pick repo type + slug
Ask (one round): build repo (code/deploys → init.sh flavor) or knowledge repo (OKF KB → ClaudeOS template) — or both. Default slug = the project's local-folder name. Confirm the destination ~/gits/<slug> with the user.
Step 2 — Scaffold the repo
- build:
mkdir -p ~/gits/<slug> && git -C ~/gits/<slug> init, thenbash ~/gits/clybor-claude-tooling/scripts/init.sh ~/gits/<slug> "<Display Name>"(copies the.claude/tree,CLAUDE.md, PRD templates,check-knowledge.sh+ pre-commit gate). - knowledge: copy your ClaudeOS OKF-bundle master template (the self-replicating
.claudeos-templateknowledge base) per itsprocedures/new-project.md(the marker travels with the copy; first-run configures the instance). NEVER write content into a folder while its.claudeos-templatemarker is present. - Then invoke
project-bootstrapto install matching catalog assets + writeTOOLING.md.
Step 3 — Write the spine (the bridge)
Anchor on the Notion Project ID from Step 0.
- life-crm side — set
~/gits/life-crm/<folder>/index.mdfrontmatter:role: crm,notion_project: <id>,canonical_repo: ~/gits/<slug>(or arepos:list for multi-repo). If the folder has noindex.md, create one to the Clybor OKF profile (schema: okf-adapted-v0.1); reframe local deliverables as client-delivery renders (canon now lives in the repo). - gits side (two-way ONLY — optional): add
~/gits/<slug>/index.mdwithrole: build|knowledge,notion_project: <id>,crm_home: ~/gits/life-crm/<folder>. Skip unless the user opens the repo standalone. One-way is the default.
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.
- 1mo ago First seen · 41 lines · 143 tokens per session scan A 25c9b74c8f8e
graduate-project is a skill published in the GitHub repository shawnclybor/clybor-claude-tooling (6 stars, last pushed 8d ago), licensed MIT. It adds 143 tokens to every session and 1,065 once invoked, about $0.0006 per session on Opus 5.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
quick
Execute an ad-hoc task with atomic commits. Skips full plan/review.
flo
MoFlo ticket spell - analyze and execute GitHub issues.
reset-epic
Reset an epic's test data — close PRs, delete branches, reopen issues, revert code.
yd-git-ship
A GitLab delivery workflow for coding agents. It defines how to create issues and branches, write commits, open and merge merge requests, and track continuous integration checks; continuous integration means automated checks run after changes are submitted.
teamboard
Shared team board: claim a work item before starting, hand it over, finish it. The claim is a git-ref lock, so two people cannot take the same item.
autonomous
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.