Borrowing it
Nothing to install: this file belongs to chainloop-dev/chainloop. 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/chainloop-dev/chainloop/main/.claude/skills/dependabot-pr-automation/SKILL.mdgit clone --depth 1 https://github.com/chainloop-dev/chainloopWrote 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/chainloop-dev/chainloop/dependabot-pr-automation)<a href="https://agentmods.dev/skills/chainloop-dev/chainloop/dependabot-pr-automation"><img src="https://agentmods.dev/badge/skills/chainloop-dev/chainloop/dependabot-pr-automation/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/chainloop-dev/chainloop/dependabot-pr-automation"><img src="https://agentmods.dev/badge/skills/chainloop-dev/chainloop/dependabot-pr-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Excessive Agency · line 71 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 73 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00054 | $0.00961 |
| Opus 5.5 | $0.00022 | $0.00384 |
| Sonnet 5.5 | $0.00011 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
dependabot-pr-automation 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependabot PR Automation for chainloop
This skill reviews open Dependabot pull requests, assesses their risk, approves safe ones, and merges them.
Repository Info
| Item | Value |
|---|---|
| Owner | chainloop-dev |
| Repo | chainloop |
Step 1: List Open Dependabot PRs
Use mcp__github__list_pull_requests to fetch open PRs:
owner:chainloop-devrepo:chainloopstate:open
Filter the results to only include PRs authored by dependabot[bot]. Collect each PR's number, title, head branch, and labels.
If there are no open Dependabot PRs, report that and stop.
Step 2: Assess Risk for Each PR
For each Dependabot PR, determine the risk level using these criteria:
2a. Parse Version Bump from PR Title
Dependabot PR titles follow the pattern: Bump <package> from <old-version> to <new-version>. Extract the old and new versions and classify the bump:
| Bump Type | Risk Level | Criteria |
|---|---|---|
| Patch (x.x.OLD → x.x.NEW) | Low | Only the patch segment changed |
| Minor (x.OLD.x → x.NEW.x) | Medium | The minor segment changed |
| Major (OLD.x.x → NEW.x.x) | High | The major segment changed |
2b. Check CI / Check Status
Use mcp__github__get_pull_request_status to retrieve the CI check status for each PR. A PR is considered CI-passing only if all checks have concluded with a success state.
2c. Inspect the Diff
Use mcp__github__get_pull_request_files to review the files changed. Flag any PR that modifies unexpected files beyond dependency manifests (go.mod, go.sum, package.json, yarn.lock, Dockerfile*, .github/workflows/*).
2d. Identify Dependency Scope
- Development-only (test frameworks, linters, dev tools) → Lower risk
- Production (runtime dependencies) → Higher risk
- GitHub Actions (workflow dependencies) → Typically low risk for minor/patch bumps
2e. Final Risk Matrix
| Version Bump | CI Passing | Only Manifest Files | Final Risk | Action |
|---|---|---|---|---|
| Patch | Yes | Yes | Low | Auto-approve and merge |
| Patch | No | Yes | Medium | Approve but do not merge |
| Minor | Yes | Yes | Medium | Auto-approve and merge |
| Minor | Yes | No | High | Do not approve |
| Minor | No | * | High | Do not approve |
| Major | * | * | High | Do not approve |
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 · 99 lines · 54 tokens per session scan A 0c10891c284f
dependabot-pr-automation is a skill published in the GitHub repository chainloop-dev/chainloop (606 stars, last pushed 4d ago), licensed Apache-2.0. It adds 54 tokens to every session and 961 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-01.
Other skills, from other repositories
generating-and-analyzing-sboms
Produce and ingest CycloneDX and SPDX SBOMs and correlate them to vulnerability intelligence.
implementing-secret-scanning-with-gitleaks
This skill covers implementing Gitleaks for detecting and preventing hardcoded secrets in git repositories. It addresses configuring pre-commit hooks, CI/CD pipeline integration, custom rule authoring for organization-specific secrets, baseline management for existing repositories, and remediation workflows for…
analyzing-sbom-for-supply-chain-vulnerabilities
Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…
PeerScan
Scan GitHub PR activity for engineering team assessment. USE WHEN user mentions peer scan, PR scan, GitHub activity, team assessment, engineering review, OR developer performance evidence. Generates structured reports from GitHub PR data.
summarize-changes
Summarizes uncommitted changes and flags anything risky.
secrets-gitleaks
Hardcoded secret detection and prevention in git repositories and codebases using Gitleaks. Identifies passwords, API keys, tokens, and credentials through regex-based pattern matching and entropy analysis. Use when: (1) Scanning repositories for exposed secrets and credentials, (2) Implementing pre-commit hooks to…