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/getbindu/bindu/question-answeringnpx skills add GetBindu/Bindu --skill question-answeringgit clone --depth 1 https://github.com/GetBindu/BinduWrote 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/getbindu/bindu/question-answering)<a href="https://agentmods.dev/skills/getbindu/bindu/question-answering"><img src="https://agentmods.dev/badge/skills/getbindu/bindu/question-answering.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.00003 | $0.00859 |
| Opus 5 | $0.00002 | $0.00430 |
| Sonnet 5 | $0.00001 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
question-answering 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
1 file 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 · 126 lines · 3 tokens per session scan A e6ac0fb772c7
question-answering is a skill published in the GitHub repository GetBindu/Bindu (9,740 stars, last pushed 4d ago), with no licence file. It adds 3 tokens to every session and 859 once invoked, about $0.0000 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-30.
Other skills, from other repositories
inspect_ai_requests
Follow one inference request through the AI gateway: from the client's /v1/messages call, through model routing and the governance pipeline, to the provider and back. Use it to debug a single request - routing, denials, latency, cost, or the tool calls it spawned.
agent-orchestrator
Use when building an agent system — an orchestrator, an LLM-powered tool, a chatbot with tool use, an AI pipeline — or metering and billing the LLM access it burns. Covers tool-calling loops, pipelines with human checkpoints, provider routing with fallback/retry, memory architecture, retrieval and decay, context…
prompt-cache-agent-harness
Plan and inspect prompt-cache behavior for long-running Claude agent loops. Use when a user wants to split stable tool, system, and history context into cacheable layers, compare captured cache metadata, estimate cost impact from supplied pricing inputs, or keep durable memory outside the cached prefix.
Rust Standards
Complete Rust coding, linting, testing, architecture, and layer boundary standards for systemprompt.io development.
Web Standards
Extension system, content templates, page prerendering, and CSS management standards for systemprompt.io web development.
Architecture Standards
Layer architecture, module boundaries, extension patterns, plugin structure, config system, and build pipeline standards.