agent-harness-plugins: Instructions file for Claude Code

.github/instructions/dependabot.instructions.md

agent-harness-plugins dependabot.instructions.md is an instructions file for Claude Code, GitHub Copilot from cboone/agent-harness-plugins. It costs 1,833 tokens per session, scanned A, original, MIT.

Project-specific instructions for Dependabot facts and GitHub API conventions. Dependabot is GitHub's service for proposing dependency updates.

In plain words
What is it for?
They are for reviewing code or instructions that use Dependabot identities, security markers, and repository paths.
Why use it?
The supplied details are reference rules rather than a standalone coding feature, so they help reviewers interpret Dependabot data consistently.

Instructions file for Claude CodeGitHub Copilot

Written for Claude Code and GitHub Copilot: ${CLAUDE_PLUGIN_ROOT} variable, but also a Copilot instructions file. Also seen: mentions Claude Code; mentions Codex.

This is cboone/agent-harness-plugins's own configuration. It tells Claude Code and GitHub Copilot how to work on agent-harness-plugins itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-harness-plugins configures →

Runs only inside a plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else, and the catalogue could not identify which plugin ships it.

Reuse

Borrowing it

Nothing to install: this file belongs to cboone/agent-harness-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/cboone/agent-harness-plugins/main/.github/instructions/dependabot.instructions.md
Clone the repo
git clone --depth 1 https://github.com/cboone/agent-harness-plugins

Made for: Claude Code, GitHub Copilot.

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 agent-harness-plugins dependabot.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cboone/agent-harness-plugins/dependabot/github.svg)](https://agentmods.dev/instructions/cboone/agent-harness-plugins/dependabot)
Your own site
<a href="https://agentmods.dev/instructions/cboone/agent-harness-plugins/dependabot"><img src="https://agentmods.dev/badge/instructions/cboone/agent-harness-plugins/dependabot/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 agent-harness-plugins dependabot.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/cboone/agent-harness-plugins/dependabot"><img src="https://agentmods.dev/badge/instructions/cboone/agent-harness-plugins/dependabot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,833 This file is loaded in full into every session.
When invoked 1,833 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.01833 $0.01833
Opus 5.5 $0.00733 $0.00733
Sonnet 5.5 $0.00367 $0.00367
Haiku 4.5 $0.00183 $0.00183

Measured 3d ago against content hash 1ce4d2ce7f18, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-harness-plugins dependabot.instructions.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 3d 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.

.github/instructions/dependabot.instructions.md · 32 lines

How it starts

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

Dependabot Facts for Review

These were checked against live GitHub data and the GitHub documentation. Do not flag code or instructions that follow them.

  • One Dependabot identity, spelled per API. The gh CLI's JSON output (gh pr view --json author, gh pr list --json author) and the author:app/dependabot search qualifier use app/dependabot. REST responses (user.login on comments and reviews, author.login in the compare API) and github.actor in Actions use dependabot[bot]. gh pr list --author app/dependabot returns every Dependabot PR. Each command matches the form its own API returns, so do not ask for both forms in a comparison that reads from one API.
  • The "disable automated security fix PRs" footer line appears only on security update PRs. Version update PRs, grouped or single, do not carry it, so it is a valid security marker. A body without the footer (after a rebase, or when truncated) is reported as kind: unknown, never as version.
  • Dependabot alert manifest_path is repository-relative (go.mod, web/package-lock.json), with no leading /.
  • rust-toolchain is its own Dependabot ecosystem. It tracks rust-toolchain.toml and rust-toolchain, so neither is an untracked surface when that ecosystem is configured. pin-everything's untracked list names only .tool-versions, .nvmrc, .node-version, .ruby-version, and .python-version.
  • Dependabot supports go.work workspaces. dependabot-core #14909 (merged 2026-05-05) fetches go.work, go.work.sum, and every module its use directives name, so a single gomod entry at the workspace root covers the member modules. Do not ask for a directory per member go.mod.
  • A PR that is not a group moves each package to one version, whatever directories its files span. dependabot-core names one directory in an ungrouped PR title (pr_name_directory in message_builder.rb), and a group-by: dependency-name PR lists the same version for every directory. Files in several directories belong to one install tree, such as an npm workspace member manifest beside the root lockfile. So directory_match confirms such a PR without Bumps lines on purpose; do not ask for it to stay unconfirmed when it touches several directories.
  • Dependabot writes a digest in backticks. Dependency#humanized_version in dependabot-core renders a 40-character SHA, or an unchanged image tag's digest, as its first seven characters wrapped in backticks, in titles and body lines alike. quoted_digest reads that signal, so the letter requirement in is_sha applies only to unquoted versions.
  • base64 --decode works on macOS. The BSD base64 there accepts --decode as well as -d and -D.
  • Dependabot alerts cover a fixed set of ecosystems. GitHub's advisory ecosystems are rubygems, npm, pip, maven, nuget, composer, go, rust, erlang, actions, pub, swift, and other. Terraform, Docker, Helm, and the other version-updates-only ecosystems have no alerts, so leaving them out of the alert ecosystem map is correct.
  • Default labels. With labels unset, Dependabot applies dependencies, and adds an ecosystem label only when more than one package ecosystem is configured.
  • capture and match emit nothing when the regex does not match; they do not raise an error. [body_lines | capture(...)] on a body with no matching line is [], so the Bumps [...] fallback in updates needs no try. tests/scrut/dependabot-prs.md covers a PR with no parseable update.
  • jq on empty or whitespace-only input emits nothing and exits 0, so dependabot-prs summarize < /dev/null reaches the "input is empty" check. tests/scrut/dependabot-prs.md covers that case.
  • The close action chains gh pr comment ... && gh pr close ... on purpose. The PR is re-checked immediately before that command. Splitting the two writes around a second re-check would risk an explanatory comment on a PR that then stays open, so do not ask for the split.
  • monitor-pr:monitor treats a current-head Copilot notice on a Dependabot PR as not applicable, on purpose. An error or no-files notice means Copilot reviewed nothing at that head, the same as a missing review, which the Dependabot path already treats as n/a. That path never requests a review, so no retry can replace the notice, and leaving the Copilot axis unresolved would hold the watch open forever. Findings, drift, threads and audit items on a real current-head review still escalate.
  • refs/dependabot-triage/ belongs to the triage skill. Only dependabot:triage-prs creates refs there, so clearing the whole namespace before fetching and at wrap-up is intended.
  • Ruleset pull_request rules carry allowed_merge_methods. gh api repos/OWNER/REPO/rules/branches/BRANCH returns it in the rule's parameters (this repository's own main rule returns ["merge"]), and GitHub's REST description lists it, so reading merge methods from the rules endpoint is correct.
  • GET repos/OWNER/REPO/automated-security-fixes is a supported read. GitHub's REST description lists it as "Check if Dependabot security updates are enabled for a repository", and it returns 200 with {"enabled", "paused"} when the setting is on and 404 when it is off. Do not ask to read the setting from security_and_analysis instead.
  • The contents API does not paginate a directory listing. repos/OWNER/REPO/contents/DIR takes only path and ref, and returns up to 1,000 entries in one response, so it needs no --paginate.
  • gh api --paginate ENDPOINT --jq FILTER is valid. gh rejects --jq only together with --slurp. Without --slurp, the filter runs per page, which is correct for a filter that emits items rather than aggregating them.
  • Branch names with / need no encoding in these REST paths. repos/OWNER/REPO/branches/BRANCH, rules/branches/BRANCH, and compare/BASE...HEAD all accept a raw release/1.0-style name, verified against a live feature/... branch.
  • Commands inside the bundled script are covered by the script's permission rule. Claude Code matches allow rules against the command the agent runs, bash ".../dependabot-prs" ..., not against the gh calls the script makes internally. So gh auth token, the script's gh pr list calls, and its gh api --paginate --slurp "repos/${repo}/..." calls, double-quoted endpoints included, need no rules of their own in plugins/dependabot/README.md.
  • tests/fixtures/gh-stub accepts only the calls dependabot-prs fetch makes, on purpose. It fails on any other flag (--jq, -H) or a second operand, so a change to the script's call shape breaks the test instead of passing silently. Widen it only when the script starts making a new call. It is committed as mode 100755.
  • The script-locator fallback needs no Claude Code permission rule. It runs only when ${CLAUDE_PLUGIN_ROOT} was not substituted, which happens in Codex CLI, where Claude Code's permissions.allow rules do not apply. test -x is left out of Recommended Permissions for that reason.

Read the full file on GitHub · 32 lines

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. 3d ago Changed · -17 tokens per session 1ce4d2ce7f18
  2. 5d ago Changed · -3 tokens per session 6a4bab877a2b
  3. 10d ago Changed · +1 lines · +110 tokens per session 1625ee167aa4
  4. 1mo ago First seen · 31 lines · 1,743 tokens per session scan A 001bbacb4fb6

Subscribe to this mod's changes

agent-harness-plugins dependabot.instructions.md is an instructions file published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 1,833 tokens to every session, about $0.0073 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-15.

Related

Other instructions, from other repositories

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

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens