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 instructions/borgius/kanban-lite/core-surfacegit clone --depth 1 https://github.com/borgius/kanban-liteWhat 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.00240 | $0.00240 |
| Opus 5 | $0.00120 | $0.00120 |
| Sonnet 5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
kanban core surface 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 yesterday.
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.
What it actually says
Kanban core surface changes
- Implement shared behavior in the SDK first, then wire the API, CLI, and MCP surfaces in that order.
- Keep API, CLI, and MCP behavior in feature parity for user-facing capabilities.
- Update JSDoc when logic, parameters, return types, or behavior change; JSDoc is the source of truth for
docs/sdk.md. - Never edit generated
docs/api.md,docs/sdk.md, ordocs/webhooks.mdmanually; update the source metadata or JSDoc and regenerate them. - For user-facing changes, update
README.mdandCHANGELOG.mdin the same task.
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.
- yesterday First seen · 18 lines · 240 tokens per session scan A 033c8d81c399
kanban core surface is an instructions file published in the GitHub repository borgius/kanban-lite (6 stars, last pushed 3mo ago), licensed MIT. It adds 240 tokens to every session, about $0.0012 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 instructions, from other repositories
DevoxxGenieIDEAPlugin GEMINI.md
Instructions for devoxx/DevoxxGenieIDEAPlugin, a project described as: DevoxxGenie is an agentic plugin for IntelliJ IDEA that uses local LLM's (Ollama, LMStudio, GPT4All, Jan and Llama.cpp) and Cloud based LLMs to help review, test, explain your project code. Latest version now also supports Spec Driven Development…
squarebox CLAUDE.md
Instructions for SquareWaveSystems/squarebox, covering claude.md, agent skills, issue tracker, triage labels and domain docs.
mcpelevator CLAUDE.md
Instructions for pacnpal/mcpelevator, covering commands, architecture, conventions, agent skills and issue tracker.
clawchat-plugin-connect AGENTS.md
Instructions for XMethues/clawchat-plugin-connect, covering agent skills, issue tracker, triage labels and domain docs.
autonomous-dev CLAUDE.md
Claude Code instructions for akaszubski/autonomous-dev, covering autonomous-dev, critical rules, maintainer escape hatches, architecture and code navigation.
icloud-reminders-mcp CLAUDE.md
Claude Code instructions for Lingnik/icloud-reminders-mcp, covering icloud-reminders-mcp — project conventions, backlog: github issues, always, secrets, architecture and testing.