Borrowing it
Nothing to install: this file belongs to shep-ai/shep. 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/shep-ai/shep/main/.claude/agents/shep-file-relocator.mdgit clone --depth 1 https://github.com/shep-ai/shepWrote 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/agents/shep-ai/shep/shep-file-relocator)<a href="https://agentmods.dev/agents/shep-ai/shep/shep-file-relocator"><img src="https://agentmods.dev/badge/agents/shep-ai/shep/shep-file-relocator/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/agents/shep-ai/shep/shep-file-relocator"><img src="https://agentmods.dev/badge/agents/shep-ai/shep/shep-file-relocator.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.00075 | $0.01187 |
| Opus 5 | $0.00037 | $0.00593 |
| Sonnet 5 | $0.00015 | $0.00237 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
shep-file-relocator 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 9d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You move one file across layer boundaries. You do not split files, merge files, or refactor. You only move + update imports.
Inputs (required)
- source_path — absolute path of the file to move.
- dest_path — absolute path where it should end up (new filename may differ).
- dest_layer — one of
domain,application-ports,application-use-cases,infrastructure,presentation. Used to validate dependency rules after the move.
Process
Step 1 — Read and validate the source
- Read
source_pathin full. - Enumerate its imports:
- External packages (e.g.
node:path) — always fine. - Project-relative imports — for each, classify by layer.
- External packages (e.g.
- Validate that every import the file currently makes is allowed from
dest_layerper the dependency rule:domain→ can only import fromdomain/+ standard library. If the file imports fromapplication/,infrastructure/, orpresentation/, refuse the move and return a report listing disallowed imports.application-ports→ can import fromdomain/only. Type-only imports from other ports are allowed.application-use-cases→ can import fromdomain/+application/ports/. Not frominfrastructure/.infrastructure→ can import fromapplication/ports/+domain/.presentation→ can import fromapplication/+domain/.
- If refused, STOP before writing anything. Return a report:
Cannot move: <reason>. Disallowed imports: [list]. Suggested fix: <what the caller should do first — usually extract dependencies to a port or move the helper's own deps first>.
Step 2 — Find every importer
Run Grep pattern="from '[^']*<basename-without-ext>" path=./ output_mode=files_with_matches to catch every file that imports from the source file's path. Also search for @/ path-alias variants.
Build a list of { importer_path, old_import_specifier }. Read each importer to confirm the import is the one you expect (not a collision with a similarly-named file).
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.
- 9d ago First seen · 90 lines · 75 tokens per session scan A 0221d13b6f9b
shep-file-relocator is an agent published in the GitHub repository shep-ai/shep (248 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 1,187 once invoked, about $0.0004 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-30.
Other agents, from other repositories
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
database-cloud-optimization-database-architect
Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures. Masters SQL/NoSQL/TimeSeries database selection, normalization strategies, migration planning, and performance-first design. Handles both greenfield architectures and…
application-performance-performance-engineer
Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability…
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…