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 agentmods add rules/andr-ca/agentharness/file-placement-policygit clone --depth 1 https://github.com/andr-ca/agentharnessWhat 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 | $0.00063 | $0.00563 |
| Opus 5 | $0.00032 | $0.00282 |
| Sonnet 5 | $0.00013 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
file-placement-policy 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 2d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Placement Policy
Load this skill at session start if the project has
.agentharness-guarded-paths.json. Read the file before touching anything.
Rule: check before creating
Before creating any new file or directory, check whether the target location is guarded:
python3 -c "
import json
d = json.load(open('.agentharness-guarded-paths.json'))
print('Root guarded:', d['guard_root_level_new_items'])
print('Guarded dirs:', d['guarded_dirs'])
"
If the path is guarded: stop and ask the user for permission.
What counts as guarded
- Any new file at the root level (when
guard_root_level_new_items: true) - Any file under
src/,docs/,tests/,conf/,logs/, etc. - Any root-level config file already listed in
guarded_root_files
Asking for permission
"I need to create
docs/architecture/NEW_SECTION.mdto document X. This is in the guardeddocs/directory. May I proceed?"
Wait for an explicit yes/ok/go ahead response.
After getting permission: record it
Add the approved path to .agentharness-allowed-additions.txt:
echo "docs/architecture/NEW_SECTION.md" >> .agentharness-allowed-additions.txt
The pre-commit hook reads this file to allow the commit.
No guarded-paths file = early-stage project
If .agentharness-guarded-paths.json doesn't exist:
- Run:
python3 tools/analyze_structure.py . --recommend - Present the recommendations to the user.
- If accepted, create the structure and generate the config:
python3 tools/analyze_structure.py . --output .agentharness-guarded-paths.json
Pre-commit enforcement
The hook at tools/check-file-placement.sh runs automatically before
every commit. If a staged file is in a guarded location and not in
.agentharness-allowed-additions.txt, the commit is blocked with a
clear message.
Reference
Full protocol: patterns/file-placement-policy/POLICY.md
Analyzer: tools/analyze_structure.py
Hook: tools/check-file-placement.sh
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.
- 2d ago First seen · 70 lines · 63 tokens per session scan A e0ed9bf0d6db
file-placement-policy is a cursor rule published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 563 once invoked, about $0.0003 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-08-31.
Other cursor rules, from other repositories
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
handoff
Export a Waybill Bundle by default, or import one when explicitly requested.
cursorrules
This repo has a GraphPilot structural code-graph available via MCP. Use it before grep on structural questions.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.
lemoncrow.execute
LemonCrow execute mode reference for Cursor.