Borrowing it
Nothing to install: this file belongs to eidos-agi/resume-resume. 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/eidos-agi/resume-resume/master/.claude/commands/prep-for-public.mdgit clone --depth 1 https://github.com/eidos-agi/resume-resumeWrote 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/commands/eidos-agi/resume-resume/prep-for-public)<a href="https://agentmods.dev/commands/eidos-agi/resume-resume/prep-for-public"><img src="https://agentmods.dev/badge/commands/eidos-agi/resume-resume/prep-for-public/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/commands/eidos-agi/resume-resume/prep-for-public"><img src="https://agentmods.dev/badge/commands/eidos-agi/resume-resume/prep-for-public.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.00000 | $0.00977 |
| Opus 5 | $0.00000 | $0.00489 |
| Sonnet 5 | $0.00000 | $0.00195 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
prep-for-public 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prep-for-public
Audit this repo for public release readiness. Run every check below, report findings as READY / CONCERN / BLOCKER.
Security Checks (BLOCKERS if found)
- Hardcoded secrets: Scan all non-.gitignore files for patterns: API keys (
sk-,ghp_,evk_,pypi-,AKIA), passwords, tokens, private URLs, connection strings with credentials - Private SSH deps: Check
pyproject.toml,package.json,requirements*.txtforgit+ssh://orgit+https://github.com/private repo refs - Internal hostnames: Search for
.internal,localhosthardcoded as production URLs, private IP ranges (10.x, 192.168.x, 172.16-31.x) - Sensitive env files: Verify
.env,.env.local,*.pem,*.key,credentials.jsonare in.gitignoreand not committed - Git history secrets: Run
git log --all --onelineand flag if any commit messages mention secrets, passwords, or tokens
Identity & Attribution
- Author info: Does
pyproject.toml/package.jsonhave correct author name + email? - License: Does a
LICENSEfile exist in root? Does it match the declared license in pyproject? - Copyright headers: Are any source files missing attribution that require it?
Install & Dependency Checks
- All deps on public registries: No
git+ssh://, no private PyPI indexes, no internal npm registries - Version pinned appropriately: No
*or missing version constraints on critical deps - Install actually works:
pip install -e .ornpm installcompletes without errors - Entry points work: Run the installed CLI commands and verify they start without crashing
Documentation
- README exists and has: Title, one-line description, install instructions, basic usage example, license badge or mention
- Install instructions are current:
pip install <name>uses the actual published package name - No internal references in docs: No mentions of internal systems, private repos, or internal URLs
- Examples work: Any code examples in README are runnable
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 · 78 lines · 0 tokens per session scan A 6f8a66d1ce05
prep-for-public is a command published in the GitHub repository eidos-agi/resume-resume (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 977 tokens. 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.