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/wlfghdr/agentic-kb/kb-tracker-workflownpx skills add wlfghdr/agentic-kb --skill kb-tracker-workflowgit clone --depth 1 https://github.com/wlfghdr/agentic-kbWrote 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/wlfghdr/agentic-kb/kb-tracker-workflow)<a href="https://agentmods.dev/skills/wlfghdr/agentic-kb/kb-tracker-workflow"><img src="https://agentmods.dev/badge/skills/wlfghdr/agentic-kb/kb-tracker-workflow.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.00052 | $0.02012 |
| Opus 5 | $0.00026 | $0.01006 |
| Sonnet 5 | $0.00010 | $0.00402 |
| Haiku 4.5 | $0.00005 | $0.00201 |
Grade A, and why
kb-tracker-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: KB Tracker Workflow
This repo uses tracker-backed KB primitives and the generic GitHub governance profile. The tracker is the canonical operational home for the primitive families declared in .kb-config/layers.yaml under primitive-storage.
This skill is the local operating manual for issues, projects, labels, PRs, and tracker-backed KB artifacts. It keeps agents aligned with the repository's GitHub rules before CI has to reject a PR.
Source-of-Truth Boundaries
- KB files own synthesis, evidence, reports, durable context, and file-backed primitives.
- Tracker items own operational state for every primitive family configured as
mode: tracker. - Hybrid primitives start in files and move to tracker ownership when they cross the configured sharing boundary.
- Pull requests own proposed repository changes and must link the issue or tracker item that explains why the change exists.
- Delivery systems outside GitHub may own execution state; link to them instead of copying their status into GitHub.
Never leave two active records pretending to own the same decision, task, feature, or roadmap item.
Required Preflight
Before creating or updating any tracker item:
- Read
.kb-config/layers.yaml. - Find the active layer.
- Read
connections.trackers[]andprimitive-storage. - Identify whether the requested primitive is
files,tracker, orhybrid. - Search existing KB files and tracker items for duplicates when tools are available.
- Show the proposed mutation and wait for explicit confirmation.
Before changing repository files for non-trivial work:
- Identify the linked issue or explain the small exception.
- Check native issue type, project membership, milestone, assignee, and status when the repo config requires them.
- Check parent/sub-issue placement when workstream parents are configured.
- Confirm the PR will use a closing keyword when it completes the issue.
- Identify validation commands and governed-doc or changelog impact before editing.
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 · 203 lines · 52 tokens per session scan A 5c69a85dbd05
kb-tracker-workflow is a skill published in the GitHub repository wlfghdr/agentic-kb (10 stars, last pushed 20d ago), licensed Apache-2.0. It adds 52 tokens to every session and 2,012 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
frame-macos-notification
拟真 macOS 通知 banner + app icon + 标题正文, 适合 video overlay / 产品发布预告.
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
waitlist-page
【模板: 等候名单页 / Waitlist】 【意图】为新产品 / 早鸟内测做一张极简等候页。 【布局】.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
deck-pitch
10 页融资 deck, 白底 + 蓝紫渐变 hero, traction 柱状, $X.XM ask.
conversational-ux
Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use form-design.