What is file-placement-policy?

A policy for deciding where new files and directories may be created in an established project.

It helps check project path rules before creating files in places such as the root, source code, documentation, tests, configuration, or logs.

It prevents accidental changes in protected folders or project locations and requires permission when a new path is guarded.

file-placement-policy — Skill for Claude Code by andr-ca/agentharness

Install

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.

Any agent

npx skills add andr-ca/agentharness --skill file-placement-policy

Clone the repo

git clone --depth 1 https://github.com/andr-ca/agentharness

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andr-ca/agentharness/file-placement-policy/github.svg)](https://agentmods.dev/skills/andr-ca/agentharness/file-placement-policy)

Your own site

<a href="https://agentmods.dev/skills/andr-ca/agentharness/file-placement-policy"><img src="https://agentmods.dev/badge/skills/andr-ca/agentharness/file-placement-policy/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andr-ca/agentharness/file-placement-policy"><img src="https://agentmods.dev/badge/skills/andr-ca/agentharness/file-placement-policy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 594 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00067	$0.00594
Opus 5.5	$0.00027	$0.00238
Sonnet 5.5	$0.00013	$0.00119
Haiku 4.5	$0.00007	$0.00059

Measured 1mo ago against content hash 9ee0cc547702, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.claude/skills/file-placement-policy/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 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.md to document X. This is in the guarded docs/ 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

Read the full file on GitHub · 89 lines

Changes

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 · 89 lines · 67 tokens per session scan A 9ee0cc547702

Subscribe to this mod's changes

file-placement-policy is a skill published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 594 once invoked, about $0.0003 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.

Claude Code agent-skills ai-agents coding-agents developer-tools

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

cdf-anomalygen

Use when running the CDF AnomalyGen pipeline over a defect dataset — mask placement, fine-tuning, synthetic defect-image generation (SDG), evaluation, quality refinement, and pseudo-labeling — even when the user names only one stage.

NVIDIA/skills · 54 tokens

deepstream-sop

Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via event boundary detection (GEBD) plus VLM classification. Trigger even if the…

NVIDIA/skills · 219 tokens

file-placement-policy