Borrowing it
Nothing to install: this file belongs to kruchenburger/another-s3-manager. 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/kruchenburger/another-s3-manager/main/CLAUDE.mdgit clone --depth 1 https://github.com/kruchenburger/another-s3-managerWrote 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/instructions/kruchenburger/another-s3-manager/claude-md)<a href="https://agentmods.dev/instructions/kruchenburger/another-s3-manager/claude-md"><img src="https://agentmods.dev/badge/instructions/kruchenburger/another-s3-manager/claude-md.svg" alt="Measured on agentmods" 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.05348 | $0.05348 |
| Opus 5 | $0.02674 | $0.02674 |
| Sonnet 5 | $0.01070 | $0.01070 |
| Haiku 4.5 | $0.00535 | $0.00535 |
Grade A, and why
another-s3-manager 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.
How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Another S3 Manager
Lightweight web UI for managing files in S3 and S3-compatible storage.
This is a public repository. Never commit, push, or include in PR descriptions / commit messages / issue bodies any absolute paths from a developer's local filesystem (e.g.
D:\...,/Users/...,C:\...,/home/...). Specs and plans for this project live out-of-repo per.claude/rules/specs-and-plans.md— when referencing them in a PR description, use only the relative tail (e.g.specs/2026-05-02-foo-design.md (out-of-repo)), never the full absolute path. Personal directory structure leaking into a public repo is a privacy issue and looks unprofessional.
Stack
- Backend: Python 3.13+, FastAPI, Boto3, JWT auth (cookie-based), per-username ban for brute-force defense
- Frontend: React + Mantine (Vite); FastAPI serves the built SPA at
/ - Deployment: Docker, Docker Compose, Kubernetes (chart hosted at github.com/kruchenburger/helm — in progress)
- Package manager: uv
Structure
another-s3-manager/
├── src/
│ └── another_s3_manager/
│ ├── __init__.py
│ ├── main.py # FastAPI app, API endpoints
│ ├── auth.py # JWT auth, CSRF, ban logic
│ ├── config.py # Config management (config.json)
│ ├── constants.py # App constants, paths
│ ├── database.py # SQLAlchemy engine + session_scope()
│ ├── models.py # ORM models (User, Role, Ban)
│ ├── s3_client.py # S3 client, role management
│ ├── users.py # User management (SQLite via SQLAlchemy)
│ ├── utils.py # Validation, sanitization
│ └── static/app/ # React SPA build output (generated, not tracked)
├── migrations/ # Alembic migrations (env.py + versions/)
├── alembic.ini
├── tests/ # pytest tests
├── frontend/ # React + Mantine source
├── data/ # Runtime data (not tracked)
├── pyproject.toml
├── Dockerfile
├── docker-compose.yml
└── uv.lock
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.
- 7d ago First seen · 310 lines · 5,348 tokens per session scan A 6742be191f2b
another-s3-manager CLAUDE.md is an instructions file published in the GitHub repository kruchenburger/another-s3-manager (5 stars, last pushed 1mo ago), licensed MIT. It adds 5,348 tokens to every session, about $0.0267 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 instructions, from other repositories
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.
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).
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.
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.
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).
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.