agentmods.dev

woodpecker-ci

woodpecker-ci is a skill for Claude Code, Codex from magnus919/agent-skills. It costs 87 tokens per session (2,074 once invoked), scanned A, original, MIT.

An operating guide for Woodpecker CI, a system that runs automated build and test workflows when code changes. It covers the server, worker agents, forge connections, pipelines, secrets, and Docker or Kubernetes backends.

In plain words
What is it for?
Use it to install or administer Woodpecker CI, connect it to Forgejo or Gitea, write and validate pipelines, manage secrets, run the command-line client, and troubleshoot failed builds.
Why use it?
It gives developers a method for setting up CI and locating failures at the correct layer instead of changing unrelated configuration. It also stresses checking configuration and service health after changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 176repo +5 yesterday A scan SkillSpector: warn 87 tokens original MIT

Good fit Use it to install or administer Woodpecker CI, connect it to Forgejo or Gitea, write and validate pipelines, manage secrets, run the command-line client, and troubleshoot failed builds.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/magnus919/agent-skills/woodpecker-ci
View source ↗ magnus919/agent-skills
Install

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.

Any agent
npx skills add magnus919/agent-skills --skill woodpecker-ci
Clone the repo
git clone --depth 1 https://github.com/magnus919/agent-skills

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin woodpecker-ci — /plugin install woodpecker-ci after adding the marketplace above.

Wrote 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.

agentmods badge for woodpecker-ci

README.md
[![agentmods](https://agentmods.dev/badge/skills/magnus919/agent-skills/woodpecker-ci/github.svg)](https://agentmods.dev/skills/magnus919/agent-skills/woodpecker-ci)
Your own site
<a href="https://agentmods.dev/skills/magnus919/agent-skills/woodpecker-ci"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/woodpecker-ci/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.

agentmods 80×15 button for woodpecker-ci

Your own site · 80×15
<a href="https://agentmods.dev/skills/magnus919/agent-skills/woodpecker-ci"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/woodpecker-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,074 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

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 →

  • high Privilege Escalation · line 52
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.02074
Opus 5.5 $0.00035 $0.00830
Sonnet 5.5 $0.00017 $0.00415
Haiku 4.5 $0.00009 $0.00207

Measured 2mo ago against content hash 201f2221575c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

woodpecker-ci 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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/woodpecker-doctor.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

woodpecker-ci/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Woodpecker CI

Use this skill as an operating playbook, not as a substitute for checking the documentation for the installed major version. Prefer explicit SemVer image tags, verify the resolved configuration before starting services, and verify runtime health after every change.

Scope boundary: This skill configures and operates Woodpecker CI (the server, agents, workflows, and integrations). It does not install or administer Forgejo/Gitea itself, and it does not configure Forgejo Actions runners. When a task mentions Forgejo, treat it as the forge Woodpecker connects to unless forge administration is explicitly requested.

Operating loop

  1. Identify the Woodpecker major version, forge, backend, deployment files, database, public URL, and whether the task is a setup, pipeline, or incident.
  2. Read the matching reference below before changing configuration.
  3. Render and lint configuration before starting the server or agent.
  4. Make the smallest change at the layer that owns the problem: forge/OAuth, server, agent/backend, or repository workflow.
  5. Verify the result at the next boundary: server health, agent connected state, repository webhook, pipeline scheduling, step logs, and external deployment endpoint.
  6. Record the exact version and relevant environment variables without recording secret values.

Choose the entry point

If the task is... Start here
New server/agent or forge connection references/setup.md
Workflow YAML, services, conditions, secrets, or plugins references/pipeline-syntax.md
Upgrade, backup, metrics, CLI, or capacity references/operations.md and references/advanced-patterns.md
A failed login, queued pipeline, clone, step, or backend references/troubleshooting.md and references/failure-signatures.md
A trust or multi-tenant decision references/security.md and the backend section of references/setup.md
Local lint/exec or CLI installation references/cli.md

Read the full file on GitHub · 133 lines

Files

What ships with it

16 files 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.

Changes

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.

  1. 2mo ago First seen · 133 lines · 87 tokens per session scan A 201f2221575c

Subscribe to this mod's changes

woodpecker-ci is a skill published in the GitHub repository magnus919/agent-skills (176 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 2,074 once invoked, about $0.0003 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-05.

CI and CDDevOps and cloudLLMagent-skillsagentskillsai-agentsautomation
Related

woodpecker-ci compared with skills from other repositories

woodpecker-ci next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
woodpecker-cimagnus919/agent-skillsSkill176yesterdayMITA87Claude Code, Codex
autonomous-loopsaffaan-m/ECCSkill302k5d agoMITA26Claude Code, Kiro
deployment-patternsaffaan-m/ECCSkill302k5d agoMITA41Claude Code, Kiro
mcp-dependency-reviewaffaan-m/ECCSkill302k5d agoMITA52Claude Code, Codex
baby-sitlangchain-ai/open-sweSkill11ktodayMITA30Claude Code, Codex
cocowatchSnowflake-Labs/cocoplusSkill7296d agoMITA43Claude Code
cocoplus-configSnowflake-Labs/cocoplusSkill7296d agoMITA56Claude Code