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/borgius/kanban-lite/plugin-options-schema-authornpx skills add borgius/kanban-lite --skill plugin-options-schema-authorgit clone --depth 1 https://github.com/borgius/kanban-liteWrote 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/borgius/kanban-lite/plugin-options-schema-author)<a href="https://agentmods.dev/skills/borgius/kanban-lite/plugin-options-schema-author"><img src="https://agentmods.dev/badge/skills/borgius/kanban-lite/plugin-options-schema-author.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.00067 | $0.01074 |
| Opus 5 | $0.00034 | $0.00537 |
| Sonnet 5 | $0.00013 | $0.00215 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
plugin-options-schema-author 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 3d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Options Schema Author
Use this skill whenever you are creating or changing plugin settings schemas for kanban-lite providers.
This skill exists to keep schema-driven plugin settings consistent across:
- provider exports,
- the shared Settings panel Plugin Options UI,
- SDK/API/CLI/MCP transport payloads,
- secret redaction behavior,
- and contributor-facing docs/tests.
When this skill applies
Load this skill before making changes when the task involves any of the following:
optionsSchema()uiSchemaoptionsSchemaspolicyOptionsSchemasPluginSettingsOptionsSchemaMetadata- JSON Forms controls/layouts/rules for plugin options
- secret field metadata for plugin settings
- schema-driven provider configuration in the shared Plugin Options workflow
First moves
Before editing files:
- Read the current provider schema source.
- Read
docs/plugins.mdsections covering plugin settings andoptionsSchema(). - Read the relevant UI consumer when needed (for example
packages/kanban-lite/src/webview/components/SettingsPanel.tsx). - If the task mentions JSON Forms behavior, consult the JSON Forms docs for:
- controls
- layouts
- rules
Core workflow
1. Keep schema, uiSchema, and secrets aligned
Every change to a provider options contract should review all three pieces together:
schemadefines the data contractuiSchemadefines the editing experiencesecretsdefines masking/write-only behavior
Do not update one and forget the others.
2. Prefer explicit uiSchema for non-trivial shapes
If the schema contains arrays, nested objects, or conceptually separate sections, prefer an explicit uiSchema instead of relying on the generated fallback.
Especially provide uiSchema when you need:
- section grouping,
- inline array item editors,
- stable labels,
- enum presentation tweaks,
- or conditional enable/show/hide behavior.
3. Use JSON Forms primitives intentionally
Prefer these patterns:
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.
- 3d ago First seen · 141 lines · 67 tokens per session scan A b4967de82051
plugin-options-schema-author is a skill published in the GitHub repository borgius/kanban-lite (7 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 1,074 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…