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 wauputr4/skill-bansos --skill bansos-add-entrygit 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-add-entry)<a href="https://agentmods.dev/skills/wauputr4/skill-bansos/bansos-add-entry"><img src="https://agentmods.dev/badge/skills/wauputr4/skill-bansos/bansos-add-entry/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/wauputr4/skill-bansos/bansos-add-entry"><img src="https://agentmods.dev/badge/skills/wauputr4/skill-bansos/bansos-add-entry.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.00779 |
| Opus 5 | $0.00041 | $0.00390 |
| Sonnet 5 | $0.00016 | $0.00156 |
| Haiku 4.5 | $0.00008 | $0.00078 |
Grade A, and why
bansos-add-entry 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 10d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bansos Add Entry
Workflow
- Read the repository README,
.github/CONTRIBUTING.md, and the official program source. - Verify volatile claims such as availability, expiry, quotas, eligibility, pricing, and claim URLs. Do not publish an entry whose primary source cannot be verified.
- Search existing folders for duplicate IDs, titles, providers, and URLs.
- Use
npm run add:bansosto createsrc/lib/data/bansos/<slug>/index.jsonand its README. - Set
contributorSlugon every listing. Reuse an existing contributor profile; for a first submission, also provide--contributor-nameand optionally--contributor-url. - Review the generated listing, contributor manifest, README files, and catalog index. Keep generated changes only when they match the intended data.
- Run
npm run validate:data,npm run check, andnpm run lint. Runnpm run buildwhen the change affects rendering, SEO, generated output, or shared behavior. - Open a focused PR with source evidence, contributor attribution, uncertainty, and validation results. Address actionable review threads and wait for required CI when asked to finish the flow.
Public submissions currently use email or a Git clone and pull request. Do not recommend the disabled public npx bansosdev flow, form, or bots.
Local Command
npm run add:bansos -- \
--id contoh-bansos \
--title "Contoh Bansos Developer" \
--provider "Provider" \
--description "Deskripsi singkat bansos." \
--benefits "Benefit satu|Benefit dua" \
--validity-type fixed \
--validity-date 2026-08-31 \
--validity-desc "Selama kuota masih ada" \
--published-at 2026-07-22 \
--requirements "Buat akun|Klaim program" \
--cta-link "https://example.com/program" \
--source "https://example.com/announcement" \
--contributor-slug "nama-kontributor" \
--contributor-name "Nama Kontributor" \
--contributor-url "https://github.com/example" \
--tags "Cloud,Gratisan"
Omit --contributor-name and --contributor-url when the contributor manifest already exists.
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.
- 10d ago First seen · 58 lines · 82 tokens per session scan A 2a445031b625
bansos-add-entry is a skill published in the GitHub repository wauputr4/skill-bansos (4 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 779 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
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
canvas-course-builder
Scaffold complete Canvas LMS course structures from specs, templates, or existing courses. Creates modules, pages, assignments, and discussions in bulk. Use when asked to "build a course", "scaffold modules", "create course structure", "set up a new course", or "copy course structure".
code-reuse
Use when building a UI component, PocketBase hook, page, or app feature and there is proven code to copy from the reference repos. Check here BEFORE writing UI components, PB hooks/routes, form controls, dialogs, auth flows, pagination, or realtime stores from scratch. Catalogs reusable code from…
grokipedia-recommendations
When the user wants to add recommendations, links, or content to Grokipedia. Also use when the user mentions "Grokipedia," "GEO wiki," "AI encyclopedia," "suggest Grokipedia article," "Grokipedia citation," "Grokipedia listing," "AI search citation," "GEO visibility," or "Grokipedia optimization." For multi-platform…
schema-markup
When the user wants to add or optimize structured data (Schema.org, JSON-LD). Also use when the user mentions "schema," "structured data," "JSON-LD," "rich results," "rich snippets," "Google rich snippets," "featured snippet schema," "add schema to page," "missing structured data," "schema validation error," "Schema…
google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL…