Borrowing it
Nothing to install: this file belongs to solana-foundation/solana-developer-platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/solana-foundation/solana-developer-platform/main/.agents/skills/sdp-bug-report/SKILL.mdgit clone --depth 1 https://github.com/solana-foundation/solana-developer-platformWrote 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/solana-foundation/solana-developer-platform/sdp-bug-report)<a href="https://agentmods.dev/skills/solana-foundation/solana-developer-platform/sdp-bug-report"><img src="https://agentmods.dev/badge/skills/solana-foundation/solana-developer-platform/sdp-bug-report/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/solana-foundation/solana-developer-platform/sdp-bug-report"><img src="https://agentmods.dev/badge/skills/solana-foundation/solana-developer-platform/sdp-bug-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 66 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00061 | $0.00989 |
| Opus 5.5 | $0.00024 | $0.00396 |
| Sonnet 5.5 | $0.00012 | $0.00198 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade B, and why
sdp-bug-report scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
2. Immediately `curl -X PUT --data-binary @file` to the returned URL with the returned headers verbatim (signed URL dies in 60s — never batch other work between prepare and PUT). Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Immediately `curl -X PUT --data-binary @file` to the returned URL with the returned headers verbatim (signed URL dies in 60s — never batch other work between prepare and PUT). How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sdp-bug-report
File one bug to Linear under the bug-bash epic, with a screenshot proving it. This is the one sanctioned exception to "skills file to GitHub Issues" — bug-bash bugs go to Linear because the epic lives there.
Fixed coordinates:
- Team: Product Engineering (id
8b2a5825-10f9-469c-b547-a1d57629b16c) - Parent: PRO-1482 (Epic: SDP Ongoing Bug Bash)
Required capabilities
Resolve tools by capability rather than by agent-specific names:
- Linear issue creation and issue-description updates.
- Linear inline-asset upload preparation.
- Browser tab inspection, navigation, interaction, JavaScript execution, and screenshots saved to disk.
Claude Code may expose these through Linear MCP and browser-extension tools; Codex may expose them through apps, MCP connectors, or browser/computer tools. If the required Linear capability is unavailable, stop before filing and state which connector is missing. Do not file the bug in another tracker.
Workflow
1. Extract the bug from the conversation
Pull from what the reporter already said: what they did, what they expected, what actually happened, and where (URL/page, local vs deployed). Ask ONE batched question only for genuinely missing essentials — never a multi-turn interview. If they pasted an error or described steps, that's enough; don't re-ask what's already in the conversation.
2. Reproduce in the browser, highlight, screenshot
Inspect the current browser tabs first, then create a new tab so the reporter's existing tabs are not hijacked. Chromium-compatible browser tools are sufficient; do not assume the browser product from the tool name.
- Navigate to the affected page (local dev at
http://localhost:3000unless he says deployed). - Perform the repro steps until the bug is visible on screen.
- Highlight the buggy element with a red box through the browser's JavaScript capability — the lightest possible path, no image-editing tools needed:
const el = document.querySelector('<selector for the buggy element>'); el.style.outline = '3px solid #ef4444'; el.style.outlineOffset = '2px'; - Save a browser screenshot to disk and retain the returned file path. Do NOT use
screencapture/osascript(they can target the wrong browser and require terminal Screen Recording permission). - Remove the outline afterwards (set
el.style.outline = '') so the page is clean if the reporter keeps the tab.
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.
- 1mo ago First seen · 74 lines · 61 tokens per session scan B 5d4bed366965
sdp-bug-report is a skill published in the GitHub repository solana-foundation/solana-developer-platform (58 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 989 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…