agentmods.dev

sancho-fetch: Instructions file for Claude Code

CLAUDE.md

sancho-fetch CLAUDE.md is an instructions file for Claude Code from panth-net/sancho-fetch. It costs 2,126 tokens per session, scanned A, a copy of sancho-fetch AGENTS.md, Apache-2.0.

Repository instructions for Sancho Fetch, a local-first library for collecting, inspecting, analysing, and exporting public data.

In plain words
What is it for?
Use them when fetching bounded data units, checking workspace status, repairing records, preparing exports, or updating Sancho.
Why use it?
They explain the tool's folders, commands, and operating rules so an agent can work without losing user data or provenance.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions AGENTS.md; mentions Codex.

This is panth-net/sancho-fetch's own configuration. It tells Claude Code how to work on sancho-fetch itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sancho-fetch configures →

not rated 0repo 11d ago A scan 2,126 tokens copy · 100% Apache-2.0
View source ↗ panth-net/sancho-fetch
Reuse

Borrowing it

Nothing to install: this file belongs to panth-net/sancho-fetch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/panth-net/sancho-fetch/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/panth-net/sancho-fetch

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.

agentmods badge for sancho-fetch CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/panth-net/sancho-fetch/claude-md.svg)](https://agentmods.dev/instructions/panth-net/sancho-fetch/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/panth-net/sancho-fetch/claude-md"><img src="https://agentmods.dev/badge/instructions/panth-net/sancho-fetch/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,126 This file is loaded in full into every session.
When invoked 2,126 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02126 $0.02126
Opus 5 $0.01063 $0.01063
Sonnet 5 $0.00425 $0.00425
Haiku 4.5 $0.00213 $0.00213

Measured 7d ago against content hash 446d3ee11586, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

sancho-fetch CLAUDE.md 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 7d 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.

Origin

This is a copy

100% identical to sancho-fetch AGENTS.md — 2 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.

CLAUDE.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md -- Sancho Fetch agent guidance

This root guide is intentionally shared by Claude, Codex, and other agents. Keep CLAUDE.md, AGENTS.md, README_ALL_INSTRUCTIONS.md, and src/sancho/templates/agent_skills/** aligned when changing operator rules.

Read this before doing anything in this repo. The user is often not a coder. Default to plain English unless sancho mode --json reports {"developer_mode": true} or the user asks for technical detail.

What Sancho Is

Sancho Fetch is a local-first data library. After setup, the visible sancho-fetch/ folder contains sancho-workspace/ with managed modules in source/**, personal work in custom/** and playbooks/**, fetched records in fetched-data/**, derived work in analysis-data/**, exports in outputs/**, logs in logs/**, and update backups in update-backups/**. The CLI is sancho.

Sancho produces inspectable facts: paths, manifests, cache status, logs, repair packets, update previews, and exports. The agent reasons about plans, explains changes, chooses bounded fetch units, and migrates user edits when needed. Sancho is not the planner.

First Steps

  1. Check mode before replying with sancho mode --json. If the command is missing or fails during first setup, default to developer mode off and use plain English. Do not open or read .env just to determine mode.
  2. Run sancho paths --json to find the active workspace. If the payload contains update_hint, relay it to the user in one plain sentence before continuing. If the sancho command is missing, fails, or lacks current commands such as setup, paths, ready, or mode, and terminal access is available, do the setup work yourself: run uv tool install sancho-fetch, then sancho setup --json (or use --path <folder> --switch-workspace only when the user explicitly wants to change an existing registered workspace). (Working from a source checkout instead? Run installers\setup.bat on Windows or bash installers/setup.sh on macOS/Linux from the repo root.) Then run sancho ready --json and retry sancho paths --json. If workspace_source == "none", run setup or sancho library register <path-to-workspace-folder> yourself. Only ask the user for help when the OS blocks execution, permissions fail, or an installer window requires human approval.
  3. Use sancho find sources "<text>" --json to pick modules; sancho inventory --json lists the full catalog when you need to browse. Never guess module IDs, request keys, or paths.
  4. For fetches, follow the installed Sancho skill. Source copies live in src/sancho/templates/agent_skills/. Confirm success from the run JSON (status, cache_status, row_count); read sancho log tail --json --limit 5 --module <id> for playbooks or failures.
  5. For updates, follow the installed Sancho update skill. Never update managed modules through raw Git.

Read the full file on GitHub · 140 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.

  1. 7d ago First seen · 140 lines · 2,126 tokens per session scan A 446d3ee11586

Subscribe to this mod's changes

sancho-fetch CLAUDE.md is an instructions file published in the GitHub repository panth-net/sancho-fetch (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 2,126 tokens to every session, about $0.0106 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sancho-fetch AGENTS.md, differing in 2 lines, and is treated as a copy.

Analytics and metricsResearch
Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens