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/wauputr4/skill-bansos/bansos-develop-featurenpx skills add wauputr4/skill-bansos --skill bansos-develop-featuregit clone --depth 1 https://github.com/wauputr4/skill-bansosWrote 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/wauputr4/skill-bansos/bansos-develop-feature)<a href="https://agentmods.dev/skills/wauputr4/skill-bansos/bansos-develop-feature"><img src="https://agentmods.dev/badge/skills/wauputr4/skill-bansos/bansos-develop-feature.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.1 | $0.00089 | $0.00618 |
| Opus 5 | $0.00044 | $0.00309 |
| Sonnet 5 | $0.00018 | $0.00124 |
| Haiku 4.5 | $0.00009 | $0.00062 |
Grade A, and why
bansos-develop-feature 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 6d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bansos Develop Feature
Workflow
- Read the repository README,
.github/CONTRIBUTING.md, nearby route/component code, and current working-tree state before editing. - Trace shared data or component callers and fix the root cause in the smallest existing abstraction.
- Preserve the SvelteKit prerender and Cloudflare Pages architecture. Do not add runtime state, secrets, or dependencies without a demonstrated need.
- Keep public routes crawlable with accurate title, description, canonical, Open Graph, and structured metadata where the repository already supports them.
- Reuse existing components, data helpers, theme tokens, icons, and responsive patterns.
- Verify desktop and mobile behavior locally. Contributor shortlink pages intentionally omit the normal header/mobile navigation but keep the footer.
- Use the folder-based add-entry flow for listing or contributor data instead of bypassing validation.
- Run the narrowest relevant checks, then prepare a focused PR with screenshots or preview notes for visual changes.
- When reviewing or merging, inspect unresolved review threads and current CI. Fix actionable findings, resolve satisfied conversations, and wait for required checks when requested.
Current Project Constraints
- App: SvelteKit with Svelte 5 and
@sveltejs/adapter-cloudflare. - Hosting and previews: Cloudflare Pages.
- Listings:
src/lib/data/bansos/<slug>/index.jsonplus optional/generated README. - Contributors:
src/lib/data/bansos/contributors/<slug>/manifest.jsonplus optional README/avatar. - Canonical contributor profiles:
https://bansos.dev/<slug>/; legacy/contributor/<slug>/is compatibility-only. - Public
npx bansosdev, form, and bot submission paths are disabled. Active public paths are email and Git clone/PR; maintainers usenpm run add:bansoslocally. - Default Latest ordering comes from
publishedAt; active Featured items belong in the featured surface rather than being duplicated in Latest. - Generated catalog, commit-history, contributor, and LLM outputs must stay synchronized through repository scripts.
What ships with it
2 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.
- 6d ago First seen · 47 lines · 89 tokens per session scan A cf278249d8c7
bansos-develop-feature is a skill published in the GitHub repository wauputr4/skill-bansos (4 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 618 once invoked, about $0.0004 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
svelte-core-bestpractices
Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.
svelte-expert
Expert knowledge in Svelte framework, SvelteKit, reactivity system, compiled approach, and building performant web applications. Use when the user mentions SvelteKit, reactivity, compiler, frontend, performance, or JavaScript, or when the task involves Svelte Fundamentals, Reactivity System, Installation and Setup, or…
svelte
Svelte 5 - Reactive UI framework with compiler magic, Runes API, SvelteKit full-stack framework, SSR/SSG, minimal JavaScript.
svelte-docs
Svelte 5.x + SvelteKit 2.x — runes, components, stores, transitions, SSR, routing, TypeScript.
vue-nuxt-frontend-patterns
Guides Vue 3 Composition API and Nuxt 3 development — composables, reactivity, SSR data fetching, and component patterns. Use when building Vue or Nuxt components, writing composables, fetching data in a Nuxt page or component, managing shared state with Pinia, or debugging a value that "isn't reactive" after being…
sveltekit
SvelteKit - Full-stack Svelte framework with file-based routing, SSR/SSG, form actions, and adapters for deployment.