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.
npx skills add 100yenadmin/fable-token-saving-skills-orchestrator --skill public-repo-operationalizergit clone --depth 1 https://github.com/100yenadmin/fable-token-saving-skills-orchestratorWrote 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/skills/100yenadmin/fable-token-saving-skills-orchestrator/public-repo-operationalizer)<a href="https://agentmods.dev/skills/100yenadmin/fable-token-saving-skills-orchestrator/public-repo-operationalizer"><img src="https://agentmods.dev/badge/skills/100yenadmin/fable-token-saving-skills-orchestrator/public-repo-operationalizer/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/skills/100yenadmin/fable-token-saving-skills-orchestrator/public-repo-operationalizer"><img src="https://agentmods.dev/badge/skills/100yenadmin/fable-token-saving-skills-orchestrator/public-repo-operationalizer.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.00034 | $0.00717 |
| Opus 5.5 | $0.00014 | $0.00287 |
| Sonnet 5.5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
public-repo-operationalizer 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 2mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Public Repo Operationalizer
Turn a useful repo into a public repo operational status surface: understandable, safe to contribute to, clear about proof, and maintainable without private context.
Core Pattern
- Audit repo truth: purpose, license, setup path, tests, CI, release state, security posture, private-data boundaries, and current claims.
- Define the public promise: what works, what is advisory, what is unproven, and what the repo does not claim.
- Add or repair default surfaces:
README.md,LICENSE,SECURITY.md,CONTRIBUTING.md,AGENTS.md,.github/ISSUE_TEMPLATE/*,.github/PULL_REQUEST_TEMPLATE.md, and focused CI. - Add claim/proof docs when claims could drift: claim audit, source authority, proof boundary, release status, and setup path.
- Wire validation: docs safety scan, tests, link/image checks, installer/package checks, and CI.
- Close with evidence: issue/PR, commands, CI URL, risks, and next action.
Public Safety Rules
- Do not publish raw transcripts, credentials, tokens, private paths, customer data, local stores, browser/session data, or screenshots with secrets.
- Say "patterns that worked for us" for practice-based guidance.
- Cite official sources near factual pricing, cache, API, legal, or security claims.
- Keep optional tools optional unless the repo truly depends on them.
Default Template Bar
Contributor-facing templates should force safe evidence:
- issue templates: public-safe reproduction and redacted logs
- docs bug templates: wrong public claim or setup step
- pull request template: linked issue, changed files, validation, safety boundary, claim impact, rollback notes, and agent-authored disclosure
Scorecard
Score each category 0-2. Pass at 14/18 or higher.
| Category | 2 means |
|---|---|
| Public promise | README says who it helps, what it does, and what it does not prove |
| First-run path | clone/install/setup/run commands work from a fresh checkout |
| Template completeness | README, license, security, contributing, AGENTS, issue templates, and pull request template fit the repo |
| Claim safety | allowed and forbidden claims are explicit and sourced where needed |
| Source/proof authority | authoritative vs advisory sources and proof boundary are clear |
| Contributor safety | redaction, no raw transcripts, no secrets, and no private paths are enforced |
| Validation automation | CI, docs safety scan, tests, and link/image checks cover the public surface |
| Release readiness | release tags, package channels, notes, or "not released yet" are clear |
| Maintainer handoff | issue/PR/evidence paths let a future agent resume |
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.
- 2mo ago First seen · 71 lines · 34 tokens per session scan A 50665381ac39
public-repo-operationalizer is a skill published in the GitHub repository 100yenadmin/fable-token-saving-skills-orchestrator (101 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 717 once invoked, about $0.0001 per session on Opus 5.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.
public-repo-operationalizer compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| public-repo-operationalizer100yenadmin/fable-token-saving-skills-orchestrator | Skill | 101 | 4mo ago | MIT | A | 34 | Claude Code, Codex |
| release-announcementpaperclipai/paperclip | Skill | 112k | today | MIT | A | 42 | Claude Code, Codex |
| releasethedotmack/claude-mem | Skill | 115k | today | Apache-2.0 | A | 13 | Claude Code |
| release-notesphuryn/pm-skills | Skill | 28k | 10d ago | MIT | A | 57 | Claude Code |
| multi-agent-release-managerchromium/chromium | Skill | 25k | today | BSD-3-Clause | A | 27 | Claude Code, Codex |
| pack-submitaeonfun/aeon | Skill | 789 | yesterday | MIT | A | 27 | Claude Code, Codex |
| updater_guidesiddsachar/row-bot | Skill | 1.7k | today | Apache-2.0 | A | 22 | Claude Code, Codex |