Borrowing it
Nothing to install: this file belongs to williamzujkowski/standards. 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/williamzujkowski/standards/master/.claude/commands/hooks/post-edit.mdgit clone --depth 1 https://github.com/williamzujkowski/standardsWrote 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/commands/williamzujkowski/standards/post-edit)<a href="https://agentmods.dev/commands/williamzujkowski/standards/post-edit"><img src="https://agentmods.dev/badge/commands/williamzujkowski/standards/post-edit/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/commands/williamzujkowski/standards/post-edit"><img src="https://agentmods.dev/badge/commands/williamzujkowski/standards/post-edit.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.00000 | $0.00581 |
| Opus 5.5 | $0.00000 | $0.00232 |
| Sonnet 5.5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
post-edit 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 yesterday.
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.
This is a copy
100% identical to post-edit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hook post-edit
Execute post-edit processing including formatting, validation, and memory updates.
Usage
npx claude-flow hook post-edit [options]
Options
--file, -f <path>- File path that was edited--auto-format- Automatically format code (default: true)--memory-key, -m <key>- Store edit context in memory--train-patterns- Train neural patterns from edit--validate-output- Validate edited file
Examples
Basic post-edit hook
npx claude-flow hook post-edit --file "src/components/Button.jsx"
With memory storage
npx claude-flow hook post-edit -f "api/auth.js" --memory-key "auth/login-implementation"
Format and validate
npx claude-flow hook post-edit -f "config/webpack.js" --auto-format --validate-output
Neural training
npx claude-flow hook post-edit -f "utils/helpers.ts" --train-patterns --memory-key "utils/refactor"
Features
Auto Formatting
- Language-specific formatters
- Prettier for JS/TS/JSON
- Black for Python
- gofmt for Go
- Maintains consistency
Memory Storage
- Saves edit context
- Records decisions made
- Tracks implementation details
- Enables knowledge sharing
Pattern Training
- Learns from successful edits
- Improves future suggestions
- Adapts to coding style
- Enhances coordination
Output Validation
- Checks syntax correctness
- Runs linting rules
- Validates formatting
- Ensures quality
Integration
This hook is automatically called by Claude Code when:
- After Edit tool completes
- Following MultiEdit operations
- During file saves
- After code generation
Manual usage in agents:
# After editing files
npx claude-flow hook post-edit --file "path/to/edited.js" --memory-key "feature/step1"
Output
Returns JSON with:
{
"file": "src/components/Button.jsx",
"formatted": true,
"formatterUsed": "prettier",
"lintPassed": true,
"memorySaved": "component/button-refactor",
"patternsTrained": 3,
"warnings": [],
"stats": {
"linesChanged": 45,
"charactersAdded": 234
}
}
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.
- yesterday First seen · 118 lines · 0 tokens per session scan A d4cc912712e4
post-edit is a command published in the GitHub repository williamzujkowski/standards (18 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 581 tokens. A static security scan graded it A with 0 findings. It is 100% identical to post-edit, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.
brain
Set up or use your Professional Brain — init, ingest, recall, or review.
context-stats
Display context window usage and token statistics.
pull-learnings
Pulls shared organization patterns into local org-patterns.toon.
perf-difficult-conversation
Three-conversations framework rehearsal (Stone/Patton/Heen — Harvard Negotiation Project) for high-stakes conversations — termination, demotion, hard feedback, conflict surfacing. Produces three-conversations breakdown (what-happened / feelings / identity), conversation script with multiple opening choices, SCARF…
culture-onboarding-90
Design a 90-day onboarding architecture for a role. First day (psychological safety + belonging activation), first week (relationship + role context + early wins), first month (skill ramp + integration + baseline), first quarter (autonomous performance + cultural integration check). Written-first elements for…