Borrowing it
Nothing to install: this file belongs to dynos-fit/dynos-work. 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/dynos-fit/dynos-work/main/CLAUDE.mdgit clone --depth 1 https://github.com/dynos-fit/dynos-workWrote 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/instructions/dynos-fit/dynos-work/claude-md)<a href="https://agentmods.dev/instructions/dynos-fit/dynos-work/claude-md"><img src="https://agentmods.dev/badge/instructions/dynos-fit/dynos-work/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.
<a href="https://agentmods.dev/instructions/dynos-fit/dynos-work/claude-md"><img src="https://agentmods.dev/badge/instructions/dynos-fit/dynos-work/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00831 | $0.00831 |
| Opus 5.5 | $0.00332 | $0.00332 |
| Sonnet 5.5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
dynos-work CLAUDE.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 10d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code and other Claude-based agents working in this repository.
Release Hygiene
Every PR that changes dynos-work ships as exactly one release. The version number is computed by CI — do not edit it by hand.
What CI does
.github/workflows/release-hygiene.yml runs on every PR open, synchronize, reopen, and label change. It calls scripts/bump_version.py, which:
- reads the current version from the PR's base ref (not from your branch),
- derives the bump from the PR title's conventional-commit prefix:
feat:is a minor bump,fix:/perf:/refactor:/docs:/chore:/test:/ci:/build:/style:/revert:are patch bumps, and a!after the type (feat!:,fix(api)!:) or the wordsBREAKING CHANGEmake it major. Arelease:major/release:minor/release:patch/release:nonelabel overrides the title. A title with no recognized prefix fails the job until it is retitled (retitling re-runs it), - stamps the resolved
release:*label on the PR (creating the label if the repo lacks it) so the bump is visible on the PR; after that, changing the label changes the bump, - writes the result to all four manifests (
package.json,.claude-plugin/plugin.json,.claude-plugin/marketplace.json,.codex-plugin/plugin.json), - adds a stub
CHANGELOG.mdsection only if no entry for that version exists, - and pushes a
chore: update release metadatacommit to your branch.
It is idempotent: re-running produces the same version, so a PR gets one version no matter how many commits it contains.
What you do
- Prefix the PR title.
feat: …for new behavior,fix: …for bug fixes,docs:/chore:/refactor:/test:/ci:for everything else,feat!:for breaking changes. The prefix decides the version, so pick it for what the change means to a plugin user, not for its size. - Pass the release label at creation. Open PRs with
gh pr create --label release:<patch|minor|major|none>matching the title's prefix. CI stamps the label anyway when it is missing, but passing it up front makes the first run deterministic and the bump visible before CI finishes. - Write the
CHANGELOG.mdentry. CI's stub is a fallback, not a substitute — it only records the PR title. Describe the behavior change, fix, or maintenance work concretely. - Leave the four manifest version fields alone. Hand-editing them is overwritten by CI, and the bot's push to your branch will reject your next
git pushuntil you rebase. - One entry per PR, not per change. If a PR bundles several logical changes, they still ship under one version. Writing an entry per change produces orphan entries for versions no manifest ever carried.
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.
- 10d ago Changed · +3 lines · +344 tokens per session b5152cf3bd84
- 2mo ago First seen · 30 lines · 487 tokens per session scan A 57cf34a612c6
dynos-work CLAUDE.md is an instructions file published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed today), licensed MIT. It adds 831 tokens to every session, about $0.0033 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-08-31.
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).
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.
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).
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.