Borrowing it
Nothing to install: this file belongs to AbdelStark/worldforge. 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/AbdelStark/worldforge/main/.codex/skills/public-docs-release/SKILL.mdgit clone --depth 1 https://github.com/AbdelStark/worldforgeWrote 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/abdelstark/worldforge/public-docs-release)<a href="https://agentmods.dev/skills/abdelstark/worldforge/public-docs-release"><img src="https://agentmods.dev/badge/skills/abdelstark/worldforge/public-docs-release/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/abdelstark/worldforge/public-docs-release"><img src="https://agentmods.dev/badge/skills/abdelstark/worldforge/public-docs-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.00594 |
| Opus 5.5 | $0.00020 | $0.00238 |
| Sonnet 5.5 | $0.00010 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
public-docs-release 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Public Docs And Release
Voice
- Serious, precise, maintainer-style.
- No hype, no tool branding, no inflated physical-fidelity claims.
- Use "integration layer" for the project frame. Treat "typed" and "local JSON" as supporting details, not the headline.
- README stays concise; route operational depth to
docs/src/playbooks.md. - Public docs should help a maintainer reproduce evidence. Avoid narrative process notes and personal collaboration context.
Synchronization Rules
| Change | Usually update |
|---|---|
| Provider capability/env var | provider docs, generated catalog, README table, .env.example, changelog, AGENTS/CLAUDE if agent-relevant |
| CLI command/help | README, docs/src/cli.md, docs/src/examples.md, help snapshots |
| Public Python API/error behavior | docs/src/api/python.md, changelog, tests, AGENTS/CLAUDE if contract-relevant |
| Runtime/smoke workflow | README, playbooks, operations, provider page, support docs |
| Docs page add/remove | mkdocs.yml and docs/src/SUMMARY.md |
| Release/version | pyproject.toml, uv.lock, README/version text, CITATION.cff, changelog, docs |
Generated Docs
Do not hand-edit provider catalog blocks. Change provider profile/catalog metadata, then run:
uv run python scripts/generate_provider_docs.py
uv run python scripts/generate_provider_docs.py --check
Operational Docs Standard
Every new runtime, provider, persistence, benchmark, or release workflow should include:
- Command to run.
- Expected success signal.
- First triage step when it fails.
Definition Of Done
- Source docs, generated docs, README tables, changelog, and navigation are synchronized for the changed public behavior.
- Generated provider catalog blocks were regenerated from metadata instead of hand-edited.
- Commands in docs are still executable or explicitly marked host-owned/credentialed/illustrative.
mkdocs build --strictand the relevant docs drift checks pass, or any skipped gate has a concrete blocker.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 59 lines · 50 tokens per session scan A f2c56f24e656
public-docs-release is a skill published in the GitHub repository AbdelStark/worldforge (108 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 594 once invoked, about $0.0002 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.
Other skills, from other repositories
dart-manage-pr
DART Manage PR: manage an open DART pull request through CI, review, merge, and cleanup.
dart-changelog
DART Changelog: decide, draft, finalize, audit, or assemble DART changelog entries.
dart-backport-pr
DART Backport PR: backport a merged main PR to a stabilization or maintenance release branch.
changelog-orchestrator
Orchestrate 6-phase changelog generation workflow with AI synthesis, multi-source data fetching (GitHub/Slack/Git), quality validation, and automated PR creation. Use when automating release notes, weekly changelogs, or documentation updates. Trigger with "generate changelog", "weekly changelog", or "automate release…
nixtla-release-validation
Multi-phase release validation workflow for nixtla. Analyzes git changes, predicts test impact, assesses risk, runs pytest verification, provides go/no-go recommendation. Trigger: "validate release", "run release validation", "check release readiness".
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.