Borrowing it
Nothing to install: this file belongs to LaurensdeGraaff/pinkbee-mcp. 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/LaurensdeGraaff/pinkbee-mcp/main/.agents/skills/mcp-development/SKILL.mdgit clone --depth 1 https://github.com/LaurensdeGraaff/pinkbee-mcpWrote 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/laurensdegraaff/pinkbee-mcp/mcp-development)<a href="https://agentmods.dev/skills/laurensdegraaff/pinkbee-mcp/mcp-development"><img src="https://agentmods.dev/badge/skills/laurensdegraaff/pinkbee-mcp/mcp-development/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/laurensdegraaff/pinkbee-mcp/mcp-development"><img src="https://agentmods.dev/badge/skills/laurensdegraaff/pinkbee-mcp/mcp-development.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.00047 | $0.00367 |
| Opus 5.5 | $0.00019 | $0.00147 |
| Sonnet 5.5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
mcp-development 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
Pinkbee MCP Development
Workflow
- Inspect related source, tests, and documentation before editing.
- For new Pinkbee endpoints, inspect supplied HAR/browser evidence when available; document the endpoint and payload instead of guessing.
- Implement matching data-source methods in
src/pinkbee_mcp/live.pyandsrc/pinkbee_mcp/mock.py, then expose a narrowly scoped tool inserver.py. - Validate all model-provided inputs, return structured JSON where appropriate, and
translate failures using the project's
ToolErrorpattern. - Gate every write with
ENABLE_WRITE_TO_PINKBEEin both the MCP tool and live client. Never make live writes unless explicitly requested. Do not retry an ambiguous write. For explicitly requested live testing, record the old value, use a date at least two months ahead, restore the change, and verify restoration. - Update README and relevant files in
docs/when behavior or configuration changes. - Run targeted tests, the full test suite, lint, and
git diff --checkwhen available. Report checks that the environment cannot run.
Rules
- Keep tool descriptions clear and specific; agents use them to decide when to call.
- Keep mock and live data-source methods aligned.
- Reuse existing patterns for timeouts, logging, configuration, and errors.
- Keep writes opt-in, narrowly scoped, and idempotent where possible.
- Keep changes simple, manageable, and documented.
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 · 30 lines · 0 tokens per session scan A f2b28b7af058
mcp-development is a skill published in the GitHub repository LaurensdeGraaff/pinkbee-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 367 once invoked, about $0.0002 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-09-27.
mcp-development compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| mcp-developmentLaurensdeGraaff/pinkbee-mcp | Skill | 0 | 1mo ago | MIT | A | 47 | Claude Code, Codex |
| mcp-tool-developersickn33/agentic-awesome-skills | Skill | 50k | yesterday | MIT | A | 38 | Claude Code |
| mem0-oss-to-platformmem0ai/mem0 | Skill | 69k | 5d ago | Apache-2.0 | A | 217 | Claude Code, Codex |
| azure-mgmt-botservice-dotnetmicrosoft/skills | Skill | 3.2k | today | MIT | A | 78 | Claude Code |
| fastapi-router-pymicrosoft/skills | Skill | 3.2k | today | MIT | A | 46 | Claude Code |
| dev-runtimelangwatch/langwatch | Skill | 5.0k | today | Apache-2.0 | A | 172 | Claude Code |
| api-designericrisco/rsc-harness | Skill | 590 | yesterday | MIT | A | 105 | Claude Code, Codex |