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 Roshu18/bearstrike-ai --skill reportinggit clone --depth 1 https://github.com/Roshu18/bearstrike-aiWrote 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/roshu18/bearstrike-ai/reporting)<a href="https://agentmods.dev/skills/roshu18/bearstrike-ai/reporting"><img src="https://agentmods.dev/badge/skills/roshu18/bearstrike-ai/reporting/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/roshu18/bearstrike-ai/reporting"><img src="https://agentmods.dev/badge/skills/roshu18/bearstrike-ai/reporting.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.00018 | $0.00381 |
| Opus 5.5 | $0.00007 | $0.00152 |
| Sonnet 5.5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
reporting 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 1mo 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.
What it actually says
reporting
Report folder structure
All reports must be saved under:
reports/output/<target_slug>//run_/
Artifacts:
- report.md
- findings.json
- metadata.json
Report type selection
1) Single bug report
Use when one confirmed high-quality issue exists.
Required sections:
- Title
- Severity
- Affected endpoint
- Reproduction steps
- PoC request
- Impact
- Remediation
2) Full pentest report
Use for multi-phase assessments.
Required sections:
- Executive summary
- Scope and methodology
- Attack surface summary
- Findings by severity
- Remediation roadmap
- Appendix (commands/artifacts)
3) Recon report
Use when no exploitable bug is confirmed but strong intel exists.
Required sections:
- Target map (hosts/services)
- Technology stack
- Exposed surfaces
- Suspicious signals for follow-up
- Next-step recommendations
Quality checklist
Before finalizing, ensure:
- Every finding has reproducible evidence.
- No finding is only a scanner claim without validation.
- Severity aligns with demonstrated impact.
- Fix guidance is concrete and actionable.
Exploit write-up quality
If exploit details are included, provide:
- Preconditions
- Step-by-step execution
- Clean expected output
- Safe rollback/mitigation notes
Evidence package standard
Each finding should include:
- request/response pair (baseline and exploit case)
- environment and account prerequisites
- deterministic reproduction steps
- impact in business language (data scope, privilege level, workflow effect)
False-positive rejection section
When closing as false positive, document:
- hypothesis tested
- why signal was non-security
- artifact proving rejection
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.
- 1mo ago First seen · 84 lines · 18 tokens per session scan A 911018523a68
reporting is a skill published in the GitHub repository Roshu18/bearstrike-ai (8 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 381 once invoked, about $0.0001 per session on Opus 5.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
gentech-blockrun
GenTech Labs' integration patterns for BlockRun MCP from Hermes Agent. Covers daily usage patterns, cost-optimized workflows, multi-tool pipelines, and reliable error handling for BlockRun's full toolset.
portainer-mcp-hygiene
How to drive the Portainer MCP server's tools correctly — both reading and mutating. Reading: project responses with select (JMESPath), where the heavy fields live (snapshots, status blocks, managed fields), how to handle non-JSON Docker/K8s proxy endpoints (container and pod logs, stats, exec), and how to interpret…
mcptoon
Compress MCP tool discovery with the mcptoon CLI. Trigger when a session has a large MCP tool catalog (many servers/tools), when the user mentions token cost, tool discovery, mcptoon, or asks to list/call MCP tools efficiently. Also route here when the user says the MCP tool list is too large, the agent context window…
kicad-library
Library management workflow for KiCAD — creating symbols, footprints, and managing libraries via MCP tools. Triggers on: "create a symbol", "make a footprint", "custom component", "register library", "find a part", "pin numbering", "new symbol", "new footprint", "add to library", "library path", "pad layout".
kicad-pcb
Workflow skill for KiCAD PCB layout and routing via MCP tools. Triggers on: "layout the board", "route traces", "PCB", "place footprints", "copper pour", "board outline", "differential pair", "board setup", "track width", "via", "zone", "design rules", "stackup", "silkscreen".
kicad-schematic
Workflow skill for KiCAD schematic design via MCP tools. Triggers on: "design a circuit", "add a component", "wire up", "connect pins", "build schematic", "place resistor", "place cap", "place IC", "schematic", "add symbol", "net label", "power rail".