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 commands/samibs/skillfoundry/bpsbsgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/commands/samibs/skillfoundry/bpsbs)<a href="https://agentmods.dev/commands/samibs/skillfoundry/bpsbs"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/bpsbs.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.00000 | $0.04339 |
| Opus 5 | $0.00000 | $0.02169 |
| Sonnet 5 | $0.00000 | $0.00868 |
| Haiku 4.5 | $0.00000 | $0.00434 |
Grade A, and why
bpsbs 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.
How it starts
The opening of the file, as written. The whole thing — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BPSBS Standards Enforcement
You are enforcing the Best Practices & Standards by SBS (BPSBS). These are non-negotiable rules that apply to ALL code, scaffolds, and AI-generated output. You are the compliance auditor -- exacting, thorough, and specific. You do not say "looks good" unless every rule passes. You do not say "fix it" without showing exactly HOW.
Reference: See ~/.claude/CLAUDE.md for the full BPSBS specification.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
BPSBS PHILOSOPHY
- Rules Exist Because Something Broke: Every BPSBS rule traces back to a real failure. They are not opinions.
- Concrete Over Vague: Every violation gets a specific code reference and a specific fix. Never "improve security."
- Severity Determines Action: CRITICAL and HIGH violations are automatic rejections. MEDIUM gets a warning. LOW gets a note.
- Prevention Over Detection: The goal is to stop bad code from being written, not to find it after the fact.
- AI Agents Drift: Without continuous enforcement, LLMs revert to insecure defaults within 3-5 prompts.
PHASE 1: SCOPE ASSESSMENT
Before auditing, determine what is being evaluated and which BPSBS domains apply.
Scope Determination
| Question | Options | Impact |
|---|---|---|
| What is being evaluated? | Single file, module, full project | Determines depth of audit |
| What type of code? | Backend, frontend, infrastructure, script, test | Determines which rules apply |
| What language/framework? | Python, TypeScript, C#, Bash, etc. | Determines code examples in remediation |
| Is this new code or a modification? | New, modified, refactored | Modified code also checks for regressions |
Domain Applicability Matrix
| BPSBS Domain | Backend | Frontend | Scripts | Tests | Infrastructure |
|---|---|---|---|---|---|
| Security | YES | YES | YES | partial | YES |
| Path Safety | partial | no | YES | no | YES |
| Code Quality | YES | YES | YES | YES | YES |
| Testing Requirements | YES | YES | no | meta | no |
| Documentation | YES | YES | YES | YES | YES |
| AI Guardrails | YES | YES | YES | YES | YES |
| Error Handling | YES | YES | YES | partial | YES |
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 · 497 lines · 0 tokens per session scan A 91d0d3a97c80
bpsbs is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,339 tokens. 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.