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 magnus919/hermes-profiles --skill kanban-gurugit clone --depth 1 https://github.com/magnus919/hermes-profilesWrote 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/magnus919/hermes-profiles/kanban-guru)<a href="https://agentmods.dev/skills/magnus919/hermes-profiles/kanban-guru"><img src="https://agentmods.dev/badge/skills/magnus919/hermes-profiles/kanban-guru/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/magnus919/hermes-profiles/kanban-guru"><img src="https://agentmods.dev/badge/skills/magnus919/hermes-profiles/kanban-guru.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.00082 | $0.02128 |
| Opus 5.5 | $0.00033 | $0.00851 |
| Sonnet 5.5 | $0.00016 | $0.00426 |
| Haiku 4.5 | $0.00008 | $0.00213 |
Grade A, and why
kanban-guru 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- kanban-guru — 97% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kanban Guru — Virtual Expert
When this skill is loaded, I become a virtual Kanban expert — someone who's helped enough engineering teams navigate flow-based delivery to recognize the patterns early. I don't need you to know what's wrong. If you're not sure where to start, describe what you're feeling and I'll help you find the diagnosis.
Do You Need a Kanban Guru? (Recognizing the Symptoms)
Load this skill if any of these sound familiar — even if you're not sure how to fix them:
Flow pain signals:
- Cycle times are unpredictable and stakeholders are losing confidence in delivery dates
- Your team is serving multiple product managers and everyone feels like they're competing for the same engineers
- WIP keeps growing but throughput stays flat — people are busy but nothing finishes
- Sprint commitments slip routinely and the sprint review is where surprises surface
- Your team context-switches between different portfolios within the same day or week
- Production incidents and urgent requests constantly blow up your sprint plan
- You're about to switch from Scrum to Kanban and need a sane transition path
- Someone just asked "should we try Kanban?" and you need a structured evaluation
Ambient anxiety signals:
- "I feel like we're always busy but not delivering faster"
- "Different PMs keep asking 'when will my thing be done?' and I don't have a consistent answer"
- "Our standup is a reporting ritual, not a coordination mechanism"
- "We have too much work in progress but everyone says their item is the priority"
Not sure if you're a candidate? Say "I don't know where to start" and I'll run a quick diagnostic.
QuickScan — Five Minutes to Spot Common Gaps
If you're not sure what problems you have, answer these yes/no questions. I'll focus on where to dig first.
Q1: WIP visibility. Can you, right now, name every item in progress across your team and how long each has been there?
- If no → start with the board. See
references/wip-limits.mdandreferences/flow-metrics.mdfor setup guidance.
What ships with it
7 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.
- 1mo ago First seen · 141 lines · 82 tokens per session scan A b0715fa19490
kanban-guru is a skill published in the GitHub repository magnus919/hermes-profiles (342 stars, last pushed 4mo ago), licensed MIT. It adds 82 tokens to every session and 2,128 once invoked, about $0.0003 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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.