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/capability-providergit 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.00397 | $0.00397 |
| Opus 5 | $0.00198 | $0.00198 |
| Sonnet 5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
capability provider invariants 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
Capability / provider invariants
card.stateandcallback.runtimeare first-class capability/provider namespaces.- Actor-scoped card state must live outside shared card content/frontmatter.
- Standalone transports that expose
card.statemust decorate cards per request/session auth context; raw shared broadcasts must not carry actor-scoped state. - Board-configured card display titles must use the shared display-title helper; raw markdown title extraction remains the source of truth for storage, filenames, and rename logic.
- Callback configuration lives in shared plugin settings; plugin enablement maps to
plugins[capability].provider, not a separate enabled boolean. - Cloudflare
callback.runtimeusesplugins["callback.runtime"].provider === "cloudflare"withtype: "module"handlers only. - Enabled Cloudflare callback module-set changes are bootstrap/redeploy gated and must fail closed on runtime drift.
- Cloudflare queue delivery is event-scoped; durable checkpoints and idempotency are tracked per handler.
- For MySQL/PostgreSQL same-provider
attachment.storage, usecreateMysqlAttachmentPlugin(engine)/createPostgresqlAttachmentPlugin(engine)instead of placeholder exports. - In-product plugin installs accept only exact unscoped
kl-*package names; reject scopes, specifiers, flags, URLs, paths, and extra args. - Plugin-settings reads, lists, errors, and install output must reuse the shared redaction policy across SDK, API, CLI, MCP, and UI surfaces.
- JSON Forms provider-option UIs should reuse the shared
.card-jsonformswrapper/styling hook instead of introducing a second theme.
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 · 20 lines · 397 tokens per session scan A c24dfec2a621
capability provider invariants is an instructions file published in the GitHub repository borgius/kanban-lite (7 stars, last pushed 3mo ago), licensed MIT. It adds 397 tokens to every session, about $0.0020 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
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.