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/danielvm-git/bigpowers/research-firstnpx skills add danielvm-git/bigpowers --skill research-firstgit clone --depth 1 https://github.com/danielvm-git/bigpowersWhat 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.00054 | $0.00775 |
| Opus 5 | $0.00027 | $0.00387 |
| Sonnet 5 | $0.00011 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
research-first 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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story: e03s01
story: e21s02
Research First
HARD GATE — Do NOT implement until prior art is searched. Minimum outcome: adopt, extend, compose, or build — with evidence.
Process
- Read
specs/product/SCOPE_LATEST.yaml,specs/release-plan.yaml + epic shards, and the current task statement. - Search in order: this repo → bigpowers skills (
search-skills) → package registries → web docs. - Check opensrc cache — if the task integrates an external library, run
bash scripts/bp-opensrc-check.sh(ornpx opensrc search <pkg>) to find locally-cached source. Read thesrc/directory for API shapes before writing any integration code. - For each candidate: note name, URL/path, fit (adopt | extend | compose | build).
- Append
## Prior Arttorequirements/SCOPE_LATEST.yamlnotes or the active epic story.
opensrc Integration
opensrc is a local cache of 200+ open-source repos and npm/PyPI packages. Query it before building any external integration to avoid re-inventing documented API shapes.
# Check if a package is cached
npx opensrc search <package-name>
# Or use the bundled helper (checks all deps from package.json or requirements.txt)
bash scripts/bp-opensrc-check.sh [package.json|requirements.txt]
If opensrc finds a match, read its src/ or source directory and append findings to the Prior Art section:
opensrc: found <pkg> v<version> — exports <key classes/functions>
If opensrc is not installed or the package is not cached, fall through to web docs normally.
Outcome matrix
| Verdict | Action |
|---|---|
| adopt | Use as-is; link in plan; no new code |
| extend | Wrap or configure existing solution |
| compose | Chain existing skills/modules |
| build | New implementation — justify why others failed |
Verify
→ verify: grep -rq 'Prior Art' specs/product specs/release-plan.yaml specs/epics 2>/dev/null
See REFERENCE.md for search commands and registry checklist.
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.
- 2d ago First seen · 88 lines · 54 tokens per session scan A 87fea8fedf7c
research-first is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 54 tokens to every session and 775 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-30.
Other skills, from other repositories
shared/tech-stack-detection
检测项目技术栈的通用方法，通过分析配置文件识别语言、框架、工具链.
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.
boss
可审计的 agent 团队：BMAD 全自动研发流水线编排器。编排 9 个专业 Agent（PM、架构师、UI Designer、Tech Lead、Scrum Master、Frontend、Backend、QA、DevOps）从需求到部署，每一步都有事件溯源 + 不可绕过门禁 + 确定性 eval——可验证测试真跑、门禁真过。支持单环节切片命令（/boss:plan /review /qa /ship）与无 CLI 纯 Markdown 降级。 Triggers: 'boss mode', '/boss', '全自动开发', '从需求到部署', '帮我做一个', 'build this', 'ship it', '全流程'…
debloat
Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved. Use when prose is correct and current but has grown verbose or patched-over and you want it tight without a full rewrite.
bmad-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".
bmad-validate-prd
Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation".