Borrowing it
Nothing to install: this file belongs to azrtydxb/procoder. 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/azrtydxb/procoder/main/.github/instructions/workflows.instructions.mdgit clone --depth 1 https://github.com/azrtydxb/procoderWrote 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/azrtydxb/procoder/workflows)<a href="https://agentmods.dev/instructions/azrtydxb/procoder/workflows"><img src="https://agentmods.dev/badge/instructions/azrtydxb/procoder/workflows/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/azrtydxb/procoder/workflows"><img src="https://agentmods.dev/badge/instructions/azrtydxb/procoder/workflows.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.00412 | $0.00412 |
| Opus 5.5 | $0.00165 | $0.00165 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
procoder workflows.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 1mo 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.
What it actually says
CI in procoder
Two tiers, kept apart on purpose: the gate answers about the change, CI answers about the tree. Do not move a whole-tree check into the gate to make a commit safer, and do not repeat the gate's answer in CI to make the pipeline look thorough.
Pins
Every tool whose answer the gate reports is pinned in
.github/tool-versions.env, for the reason that file states in its own
opening paragraph: the gate's verdict must not change because somebody
upstream released something overnight.
Installing a tool from apt is not a pin. gitleaks was installed with
apt-get install gitleaks, one line above a comment explaining that the
versions are pinned, so CI ran 8.16.0 while a developer's machine ran
8.30.1 — and the two disagreed about whether the tree contained a secret.
The gate gave two different verdicts for the same files.
A tool added to the download step must also be added to the loop that
installs those binaries onto PATH, and to the cache key. procoder doctor
runs afterwards and fails the job when one did not arrive, which is what
that step is for.
Actions
Every action is pinned by commit SHA with its tag in a trailing comment.
Every job carries timeout-minutes. Concurrency cancels in progress.
procoder ci checks all three and will tell you which is missing.
Honesty in a job
A step that could not run must fail the job or say so in its output. "Nothing to do" and "did not run" are different results and CI is the last place that distinction survives — nobody reads a green pipeline's log.
Prefer a downloaded release binary over go install …@latest: compiling
on every run cost 92 seconds for one tool, and @latest cannot be cached
or pinned.
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.
- 1mo ago First seen · 45 lines · 412 tokens per session scan A b0e53e8ae56d
procoder workflows.instructions.md is an instructions file published in the GitHub repository azrtydxb/procoder (211 stars, last pushed today), licensed Apache-2.0. It adds 412 tokens to every session, about $0.0016 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-30.
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.
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.
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).