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.
git clone --depth 1 https://github.com/skovtun/coherent-design-methodWrote 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/rules/skovtun/coherent-design-method/safe-file-transforms)<a href="https://agentmods.dev/rules/skovtun/coherent-design-method/safe-file-transforms"><img src="https://agentmods.dev/badge/rules/skovtun/coherent-design-method/safe-file-transforms/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/rules/skovtun/coherent-design-method/safe-file-transforms"><img src="https://agentmods.dev/badge/rules/skovtun/coherent-design-method/safe-file-transforms.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.00135 |
| Opus 5.5 | $0.00000 | $0.00054 |
| Sonnet 5.5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
safe-file-transforms 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
Safe File Transforms
When modifying fix.ts or adding new file transformations:
- Use
safeWrite()from./fix-validation.jsinstead ofwriteFileSyncfor all TSX/TS file writes safeWritevalidates TSX syntax after writing and rolls back on failure- Track modified files in
modifiedFilesarray for post-transform verification - Never add empty
catch {}blocks — always log withchalk.yellow - Prefer full component regeneration over regex-based patching
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 · 16 lines · 0 tokens per session scan A 7541e0552496
safe-file-transforms is a cursor rule published in the GitHub repository skovtun/coherent-design-method (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 135 tokens. 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 cursor rules, from other repositories
swamr-orchestrator
Swamr Orchestrator — autonomous agent swarm that builds entire projects. Invoke with @swamr-orchestrator followed by what you want built. Decomposes into tasks, selects specialist agents, runs dev↔QA loops, and delivers production-ready code.
swamr-planner
Swamr Planner — generates detailed project plans with task decomposition, dependency graphs, and agent assignments. Use @swamr-planner to plan before building, or let the orchestrator invoke it automatically.
swamr-obsidian-brain
Swamr Obsidian Brain — persistent knowledge base that agents read from and write to across phases. Prevents context loss by maintaining architecture decisions, task outputs, learned patterns, and project knowledge in an Obsidian vault. Every agent MUST read relevant notes before starting and write a summary note when…
swamr-browser-agent
Swamr Browser Agent — handles tasks that require browser automation via Playwright. Sets up Supabase projects, configures OAuth providers, runs visual tests, and interacts with web UIs that don't have CLI/API alternatives.
swamr-state-manager
Swamr State Manager — tracks task progress, manages the execution pipeline, handles retries and escalation. Maintains swamr/state.json as the single source of truth for swarm progress.
registry-bases-parity
Keep registry base and radix trees in sync when editing shared UI.