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 GoDiao/openkb --skill openkb-syncgit clone --depth 1 https://github.com/GoDiao/openkbWrote 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/godiao/openkb/openkb-sync)<a href="https://agentmods.dev/skills/godiao/openkb/openkb-sync"><img src="https://agentmods.dev/badge/skills/godiao/openkb/openkb-sync/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/godiao/openkb/openkb-sync"><img src="https://agentmods.dev/badge/skills/godiao/openkb/openkb-sync.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.00058 | $0.03174 |
| Opus 5.5 | $0.00023 | $0.01270 |
| Sonnet 5.5 | $0.00012 | $0.00635 |
| Haiku 4.5 | $0.00006 | $0.00317 |
Grade A, and why
openkb-sync 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenKB Sync
Agent responsibility: Every Hub page the user opens must reflect the real project.
Writing markdown that the Hub cannot load = failure (Hermes/YONOH once had blank Spec/Plan pages for this reason).
Which mode? (Agent: infer user intent first)
| User / scenario | Mode | Do not |
|---|---|---|
| "New project", "new idea", "no OpenKB project yet" | §4 New project → project create |
Do not create an existing slug |
| "Update progress", "sync board", "I did X", "continue Hermes/YONOH" | §5 Existing project · incremental sync | Do not project create; do not overwrite Spec |
| "Change Spec/Plan", "new design from discussion" | §2 + §5.3 Doc updates | Do not change code only without updating Hub |
| "Pick up task / finish / close ticket" | §5.2 Board runtime | Do not commit only without done |
One skill, two main flows: new = create; existing = context → incremental updates.
0. Environment
| Variable | Required |
|---|---|
OPENKB_ROOT |
OpenKB root directory |
OPENKB_AGENT_ID |
Agent identity |
Run: openkb.cmd … (or uv run --directory $env:OPENKB_ROOT openkb …).
For API/UI development: uv run openkb serve --port 8788 + cd web && npm run dev (5173).
1. How the Hub loads Spec / Plan (required)
Web UI /projects/{slug}/spec
→ GET /api/projects/{slug}/docs/spec
→ read project.yaml docs.spec (relative path)
→ open file: {repo_path}/{docs.spec} ← only correct location
→ return content, render Markdown
Plan page works the same way, reading docs.plan.
| Field | In project.yaml | Actual file location |
|---|---|---|
repo_path |
E:/.../hermes-agent |
Business git repo root |
docs.spec |
docs/spec.md |
E:/.../hermes-agent/docs/spec.md |
docs.plan |
docs/plan.md |
E:/.../hermes-agent/docs/plan.md |
Typical wrong-location mistakes
| Where the agent writes | Hub visible? |
|---|---|
OpenKB/workspace/projects/{slug}/spec.md |
❌ Never |
OpenKB/docs/spec.md (unless repo_path is OpenKB itself) |
❌ Usually not |
{repo_path}/docs/spec.md with set-docs registered |
✅ |
{repo_path}/other/design.md + set-docs --spec other/design.md |
✅ |
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.
- 1mo ago First seen · 356 lines · 58 tokens per session scan A d68c04b42092
openkb-sync is a skill published in the GitHub repository GoDiao/openkb (2 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 3,174 once invoked, about $0.0002 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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.