jamshid CLAUDE.md

jamshid CLAUDE.md is an instructions file for coding agents from PapaDanielVi/jamshid. It costs 1,464 tokens per session, scanned A, original, MIT.

A set of instructions for developers working in the jamshid code repository. It emphasises thinking through assumptions, keeping changes small, and avoiding unrelated edits.

In plain words
What is it for?
It is for guiding implementation decisions, clarifying uncertainty, making focused code changes, and preserving the repository's existing style.
Why use it?
It reduces unnecessary complexity and lowers the risk of changing code that was not part of the task.

Instructions file

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.

agentmods
npx agentmods add instructions/papadanielvi/jamshid/claude-md
Clone the repo
git clone --depth 1 https://github.com/PapaDanielVi/jamshid

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 jamshid CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/papadanielvi/jamshid/claude-md.svg)](https://agentmods.dev/instructions/papadanielvi/jamshid/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/papadanielvi/jamshid/claude-md"><img src="https://agentmods.dev/badge/instructions/papadanielvi/jamshid/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,464 This file is loaded in full into every session.
When invoked 1,464 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.01464 $0.01464
Opus 5 $0.00732 $0.00732
Sonnet 5 $0.00293 $0.00293
Haiku 4.5 $0.00146 $0.00146

Measured 5d ago against content hash b3615e4a3726, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

jamshid 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 5d 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.md · 88 lines

How it starts

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

1. Think Before Coding

Don't assume. Don't hide confusion. Surface tradeoffs.

Before implementing:

  • State your assumptions explicitly. If uncertain, ask.
  • If multiple interpretations exist, present them - don't pick silently.
  • If a simpler approach exists, say so. Push back when warranted.
  • If something is unclear, stop. Name what's confusing. Ask.

2. Simplicity First

Minimum code that solves the problem. Nothing speculative.

  • No features beyond what was asked.
  • No abstractions for single-use code.
  • No "flexibility" or "configurability" that wasn't requested.
  • No error handling for impossible scenarios.
  • If you write 200 lines and it could be 50, rewrite it.

Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.

3. Surgical Changes

Touch only what you must. Clean up only your own mess.

When editing existing code:

  • Don't "improve" adjacent code, comments, or formatting.
  • Don't refactor things that aren't broken.
  • Match existing style, even if you'd do it differently.
  • If you notice unrelated dead code, mention it - don't delete it.

When your changes create orphans:

  • Remove imports/variables/functions that YOUR changes made unused.
  • Don't remove pre-existing dead code unless asked.

The test: Every changed line should trace directly to the user's request.

4. Goal-Driven Execution

Define success criteria. Loop until verified.

Transform tasks into verifiable goals:

  • "Add validation" → "Write tests for invalid inputs, then make them pass"
  • "Fix the bug" → "Write a test that reproduces it, then make it pass"
  • "Refactor X" → "Ensure tests pass before and after"

For multi-step tasks, state a brief plan:

1. [Step] → verify: [check]
2. [Step] → verify: [check]
3. [Step] → verify: [check]

Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

5. Jamshid-Specific Notes

Testing: os.UserHomeDir() doesn't respect HOME env var. Use os.Getenv("HOME") in jamshidDir() for testability.

Read the full file on GitHub · 88 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. 5d ago First seen · 88 lines · 1,464 tokens per session scan A b3615e4a3726

Subscribe to this mod's changes

jamshid CLAUDE.md is an instructions file published in the GitHub repository PapaDanielVi/jamshid (5 stars, last pushed 8d ago), licensed MIT. It adds 1,464 tokens to every session, about $0.0073 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.