Borrowing it
Nothing to install: this file belongs to RikiGomes/woodpecker-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/RikiGomes/woodpecker-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/RikiGomes/woodpecker-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/instructions/rikigomes/woodpecker-mcp/claude-md)<a href="https://agentmods.dev/instructions/rikigomes/woodpecker-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/rikigomes/woodpecker-mcp/claude-md/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/instructions/rikigomes/woodpecker-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/rikigomes/woodpecker-mcp/claude-md.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.00703 | $0.00703 |
| Opus 5 | $0.00351 | $0.00351 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
woodpecker-mcp CLAUDE.md 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 10d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
woodpecker-mcp
Read-only MCP stdio server exposing Woodpecker CI pipeline status and logs. See README.md for usage; this file records the invariants that are easy to break and not obvious from any single file.
Invariants
- Read-only by contract. Only GET requests, and no restart/approve/cancel surface. Adding a write tool changes what this server is — don't, unless the request is explicitly to do so.
- stdout belongs to the JSON-RPC protocol. Never
console.log/process.stdout.writeanywhere reachable from the server: it corrupts the message stream. All human-readable output goes to stderr viaconsole.error. - The token never leaves the Authorization header. It must not appear in
logs, error messages, or URLs.
client.tsredacts it from relayed upstream error bodies; keep that when touching error paths. - Repo slugs are validated before use in a URL path.
resolveRepoIdrejects empty,.and..segments —encodeURIComponentdoes not encode., andnew URL()collapses../, so loosening this reintroduces path traversal off the/api/repos/lookup/prefix. - Config failure modes are deliberate. An incomplete named pair
(
WOODPECKER_<NAME>_URLwithout_TOKEN) warns and is skipped, because that pattern collides with real Woodpecker server/agent deployment variables. Only the unambiguous default pair fails loudly.
Conventions
- ESM throughout. Relative imports use explicit
.tsextensions (Node type stripping runssrc/directly); the build rewrites them to.js. - Erasable syntax only — no enums, no parameter properties.
- Tool input schemas are zod raw shapes.
list_instanceswraps its shape intoleratesMissingArgsso clients that omitargumentsentirely still work; the advertised JSON schema is unchanged. - Dependencies are pinned to exact versions. Bump them deliberately, and keep
npm audit --omit=dev --audit-level=highclean — CI enforces it. @types/nodetracks the minimum supported runtime, not the newest Node.enginessays>=20.12, so the types stay on 20.x: typing against a newer major lets code compile that would crash on the version this package promises to support. (process.loadEnvFile, which needs 20.12, was exactly this bug once.) Dependabot is configured to ignore its majors — raise the floor inenginesfirst if you want newer types.
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.
- 10d ago First seen · 56 lines · 703 tokens per session scan A 10b1920822d4
woodpecker-mcp CLAUDE.md is an instructions file published in the GitHub repository RikiGomes/woodpecker-mcp (0 stars, last pushed 7d ago), licensed MIT. It adds 703 tokens to every session, about $0.0035 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-09-01.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).