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.
npx skills add charlesjones-dev/claude-code-plugins-dev --skill workflow-principlesgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/workflow-principles)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/workflow-principles"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/workflow-principles.svg" alt="Measured on agentmods" 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.00030 | $0.04806 |
| Opus 5 | $0.00015 | $0.02403 |
| Sonnet 5 | $0.00006 | $0.00961 |
| Haiku 4.5 | $0.00003 | $0.00481 |
Grade A, and why
workflow-principles 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 today.
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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Principles Generator
You are a software architecture expert that generates tailored development principles for CLAUDE.md files based on a project's actual structure, technology stack, and architectural patterns.
Instructions
CRITICAL: This command MUST NOT accept any arguments. If the user provided any text or paths after this command (e.g., /workflow-principles ./src), you MUST COMPLETELY IGNORE them. You MUST ONLY gather requirements through the interactive AskUserQuestion tool and project analysis as specified below.
BEFORE DOING ANYTHING ELSE: Perform automated project discovery, then use the AskUserQuestion tool to interactively configure the principles. DO NOT skip these steps.
Phase 1: Automated Project Discovery
Before asking any questions, silently analyze the project to understand its structure. This information will be used to tailor questions and generate context-aware principles.
1.1 Project Structure Detection
Use Glob and Read to detect:
Monorepo detection:
- Check for workspace configuration:
package.jsonwithworkspacesfieldpnpm-workspace.yamllerna.jsonnx.jsonturbo.jsonrush.json- Multiple
.csprojfiles with a.slnfile Cargo.tomlwith[workspace]sectiongo.workfile
- If monorepo detected, map the workspace packages:
- Read the workspace config to get package paths
- Glob for
packages/*/package.json,apps/*/package.json,libs/*/package.json, or equivalent - Identify shared/common packages (commonly named:
shared,common,core,utils,types,contracts,lib) - Map dependency direction between packages
Single project detection:
- Standard single-package project structure
- Note the primary source directory (
src/,app/,lib/, etc.)
1.2 Technology Stack Detection
Scan for project configuration files:
Languages:
- TypeScript:
tsconfig.json(read forstrictmode, path aliases) - JavaScript:
package.jsonwithout tsconfig - C#/.NET:
*.csproj,*.sln(read for target framework, nullable reference types) - Python:
pyproject.toml,requirements.txt,setup.py - Go:
go.mod - Rust:
Cargo.toml - Java/Kotlin:
pom.xml,build.gradle
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.
- today First seen · 397 lines · 30 tokens per session scan A e19ba732cb42
workflow-principles is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 4,806 once invoked, about $0.0002 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-06.
Other skills, from other repositories
repo-guidance
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
contributor
End-to-end open source contribution workflow: from scanning issues to submitting PRs. Use this skill whenever the user wants to contribute to an open source project, find issues to fix, submit a pull request, fork a repo to contribute, fix a GitHub issue, or mentions 'open source contribution'. Also trigger when they…
git-commit-smart
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
push-all
Use when the user explicitly asks to stage all current changes, create a commit, and push to the remote after safety checks.
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…