agentmods.dev

devpowers: Instructions file for Claude Code

CLAUDE.md

devpowers CLAUDE.md is an instructions file for Claude Code from kolodkin/devpowers. It costs 857 tokens per session, scanned A, original, MIT.

A set of instructions for building and maintaining a Claude Code plugin. Claude Code is a coding assistant that can load project-specific extensions such as skills, commands, agents, and hooks.

In plain words
What is it for?
It helps organize plugin manifests and component folders, write portable skill references, and follow repository-specific setup guidance. It is documentation rather than a standalone feature.
Why use it?
It gives contributors shared rules for the plugin's file layout, references, authentication, and development conventions.

Instructions file for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions CLAUDE.md.

This is kolodkin/devpowers's own configuration. It tells Claude Code how to work on devpowers 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 devpowers 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.

not rated 2repo changed 16d ago A scan 857 tokens original MIT
View source ↗ kolodkin/devpowers
Reuse

Borrowing it

Nothing to install: this file belongs to kolodkin/devpowers. 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/kolodkin/devpowers/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/kolodkin/devpowers

Made for: Claude Code.

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 devpowers CLAUDE.md

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

agentmods 80×15 button for devpowers CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/kolodkin/devpowers/claude-md"><img src="https://agentmods.dev/badge/instructions/kolodkin/devpowers/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 857 This file is loaded in full into every session.
When invoked 857 The same file — it is already loaded in full.
Security scan A 1 finding. 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.00857 $0.00857
Opus 5.5 $0.00343 $0.00343
Sonnet 5.5 $0.00171 $0.00171
Haiku 4.5 $0.00086 $0.00086

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

Security

Grade A, and why

devpowers CLAUDE.md scanned grade A with 1 finding 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 16d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Skills that talk to GitHub (`check-pr`, `action-run`, `action-check`) authenticate through the `github` MCP server, registered via `/setup-mcp github`. It uses a single long-lived `GH_TOKEN` Personal Access Token — the
CLAUDE.md · 43 lines

How it starts

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

CLAUDE.md

This repository is a Claude Code plugin that is also its own single-plugin marketplace. The repo root is the plugin root: .claude-plugin/plugin.json is the plugin manifest, and .claude-plugin/marketplace.json catalogs it with "source": "./". Component directories (skills/, commands/, agents/, hooks/, output-styles/) live at the repo root.

Layout

.claude-plugin/
  marketplace.json              # marketplace catalog (source: "./")
  plugin.json                   # plugin manifest
skills/<skill-name>/
  SKILL.md                      # skill entry point
  ...                           # optional scripts, references
output-styles/<name>.md         # output style, listed as devpowers:<name>

Conventions

  • Reference bundled scripts from SKILL.md using plain relative paths (e.g. scripts/download.sh, scripts/update.sh). Claude resolves them against the skill's install directory, so the same SKILL.md works for both plugin installs (under ~/.claude/plugins/cache/.../skills/<name>/) and project-level installs (under <project>/.claude/skills/<name>/). Avoid ${CLAUDE_PLUGIN_ROOT} inside skill bodies — it's empty when the skill is installed project-level, and ${CLAUDE_PROJECT_DIR} isn't reliably set in Bash tool invocations either (anthropics/claude-code#6023). Reserve ${CLAUDE_PLUGIN_ROOT} for hooks/*.json and MCP/LSP configs, where the harness guarantees it's set.
  • Use ${CLAUDE_PLUGIN_DATA} for state that must survive plugin updates.
  • All component directories (skills/, commands/, agents/, hooks/, output-styles/) live at the plugin root — never inside .claude-plugin/.

GitHub auth

  • Skills that talk to GitHub (check-pr, action-run, action-check) authenticate through the github MCP server, registered via /setup-mcp github. It uses a single long-lived GH_TOKEN Personal Access Token — the same token also covers the one remaining REST curl escape hatch — the in-progress CI/run Monitor polls in all three skills — which exists because a Monitor can't call MCP tools mid-loop.
  • action-run/action-check need the MCP actions toolset, which the hosted server doesn't enable by default; skills/setup-mcp/mcps.json turns it on with the X-MCP-Toolsets: all header. Per-skill token scopes (repo/workflow, Actions: read/write, Pull requests, etc.) are documented in the README.

Read the full file on GitHub · 43 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. 16d ago Changed · +1 lines · +31 tokens per session 7469de8cbd8a
  2. 1mo ago First seen · 42 lines · 826 tokens per session scan A 7db00011e1b9

Subscribe to this mod's changes

devpowers CLAUDE.md is an instructions file published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 2d ago), licensed MIT. It adds 857 tokens to every session, about $0.0034 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

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

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

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