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-preflightgit 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-preflight)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/workflow-preflight"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/workflow-preflight.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.00029 | $0.05119 |
| Opus 5 | $0.00015 | $0.02559 |
| Sonnet 5 | $0.00006 | $0.01024 |
| Haiku 4.5 | $0.00003 | $0.00512 |
Grade A, and why
workflow-preflight 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 — 611 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preflight Code Quality Checks
You are running a comprehensive preflight check on this codebase. This command discovers and runs configured quality checks including type checking, linting, and tests.
Arguments
--fix- Automatically attempt to fix issues without prompting--check-only- Only report issues, never prompt to fix--verbose- Show detailed output from all commands- No arguments - Interactive mode (default): prompt before fixing
User provided: $ARGUMENTS
Step 1: Discovery Phase
First, analyze the project to discover configured quality tools. Check for:
Package Manager & Config Files
package.json- Check for scripts:lint,typecheck,type-check,tsc,test,check,validatetsconfig.json/jsconfig.json- TypeScript/JavaScript configuration.eslintrc*,eslint.config.*- ESLint configurationbiome.json,biome.jsonc- Biome configuration.prettierrc*,prettier.config.*- Prettier configurationdeno.json/deno.jsonc- Deno configuration.stylelintrc*- Stylelint configuration
Python Projects
pyproject.toml- Check for ruff, mypy, pytest, black, isort configssetup.py/setup.cfg- Legacy Python configrequirements.txt/requirements-dev.txt- Dependenciesmypy.ini/.mypy.ini- MyPy configurationruff.toml/.ruff.toml- Ruff configurationpytest.ini/pyproject.toml [tool.pytest]- Pytest configurationtox.ini- Tox configuration
.NET Projects
*.csproj/*.fsproj/*.vbproj- .NET project files*.sln- Solution files.editorconfig- Editor configuration with .NET analyzersDirectory.Build.props- MSBuild properties
Go Projects
go.mod- Go module.golangci.yml/.golangci.yaml- GolangCI-Lint configuration
Rust Projects
Cargo.toml- Check for clippy, rustfmtrustfmt.toml/.rustfmt.toml- Rustfmt configurationclippy.toml/.clippy.toml- Clippy configuration
Security Scanning
pnpm-lock.yaml/package-lock.json/yarn.lock- Dependency audit support.semgreprc.yml/.semgrep.yml/semgrep.yml/.semgrep/- Semgrep configuration.github/workflows/*.yml- Check for semgrep CI jobs (extract config flags)eslint-plugin-securityin devDependencies - ESLint security rulespackage.jsonscripts containingauditorsemgrep- Custom security scriptsREADME.md/CONTRIBUTING.md- Check for documented security scanning commands
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 · 611 lines · 29 tokens per session scan A 34b9070560db
workflow-preflight is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 5,119 once invoked, about $0.0001 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
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.…
dev-architecture-playbook
Route full software-development architecture work from product intent through design, implementation, testing, release, and operations. Use when the user asks for a complete development architecture, wants to know which Spellbook skills to combine, needs an execution path across…
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
ring:generating-release-guides
Generating an internal Operations-facing update/migration guide from the git diff between two refs, documenting per-change client impact, deploy ordering, monitoring, and rollback notes in English, pt-br, or both. Use when preparing a version release or recording what changed for the Ops team. Runs read-only by…
ring:creating-worktrees
Creating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from the main workspace or before executing…
coverage-check
Run the repo's unit tests with coverage and verify that every file touched in the current change keeps line, branch, and function coverage at or above 95%. Language- and framework-agnostic. Use before committing, before PR creation, or when the user asks about coverage.