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 agentmods add skills/abdelstark/worldforge/testing-validationnpx skills add AbdelStark/worldforge --skill testing-validationgit clone --depth 1 https://github.com/AbdelStark/worldforgeWhat 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 | $0.00061 | $0.00796 |
| Opus 5 | $0.00030 | $0.00398 |
| Sonnet 5 | $0.00012 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
testing-validation 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 2d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing And Validation
Choose The Gate
| Change | Minimum useful validation |
|---|---|
| Python logic | uv run pytest tests/test_target.py -q plus ruff |
| Provider behavior | provider-focused pytest, fixtures, contract helper, provider-doc check |
| CLI help/output | targeted CLI tests and help snapshots |
| Docs/provider catalog | provider-doc check and uv run mkdocs build --strict |
| Agent context/skills | skill quick_validate.py, symlink check, and git diff --check |
| Public API/package surface | full public gate below |
| TUI/harness | focused harness tests plus --extra harness coverage when relevant |
Standard Commands
Focused gate:
uv run ruff check src tests examples scripts
uv run ruff format --check src tests examples scripts
uv run pytest tests/test_target.py -q
Docs gate:
uv run python scripts/generate_provider_docs.py --check
uv run mkdocs build --strict
Public behavior/package gate:
uv lock --check
uv run ruff check src tests examples scripts
uv run ruff format --check src tests examples scripts
uv run python scripts/generate_provider_docs.py --check
uv run mkdocs build --strict
uv run pytest
uv run --extra harness pytest --cov=src/worldforge --cov-report=term-missing --cov-fail-under=90
bash scripts/test_package.sh
uv build --out-dir dist --clear --no-build-logs
Dependency audit for release work:
tmp_req="$(mktemp requirements-audit.XXXXXX)"
uv export --frozen --all-groups --no-emit-project --no-hashes -o "$tmp_req" >/dev/null
uvx --from pip-audit pip-audit -r "$tmp_req" --no-deps --disable-pip --progress-spinner off
rm -f "$tmp_req"
Rules
- Reproduce the failing command before broad edits.
- Add regression tests for bug fixes and documented failure modes.
- Keep
src tests examples scriptsin Ruff targets. - Keep
--cov-fail-under=90; add tests instead of lowering it. - Do not replace deterministic tests with live-service requirements.
- Report skipped gates with the concrete blocker.
- Match the gate to the claim: a narrow passing test never proves a broad public-release or agentic-context quality claim.
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.
- 2d ago First seen · 86 lines · 61 tokens per session scan A 4c5bc8b6100a
testing-validation is a skill published in the GitHub repository AbdelStark/worldforge (108 stars, last pushed 23d ago), licensed MIT. It adds 61 tokens to every session and 796 once invoked, about $0.0003 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-30.
Other skills, from other repositories
wellbeing
Proactive coaching across hydration, breaks, meals AND posture. Use when an [activity] event fires (message starts with [activity] Activity detected: . — labels include drink, break, celebrate, the fatigue label "yawning", or sedentary raw labels like "using computer"; sedentary events may also carry a…
faq
Explain how to run and use this repository's local Web UI, with detailed guidance for every Settings section and its visible controls. Use for questions about web development, Monitor, Setup, or Settings.
computer-use
Control the user's Mac via the paired Autonomous Buddy companion app — open/close apps, navigate URLs in Chrome, type text into focused fields, fire keyboard shortcuts, show desktop notifications, write to clipboard, click named UI buttons via macOS Accessibility. Also covers vision-driven tasks (screenshot…
connectors
Detect which third-party connectors (Gmail, Google Calendar, Google Drive, Notion, Figma, Asana, Linear, GitHub, Ahrefs, …) are connected to this device, and use them to answer or act for the user. Use when the user asks what's connected ("what connectors do I have", "is my gmail connected", "did I link figma"), or…
mood
Tracks the USER's mood only — signals + synthesized decision from camera/voice/telegram. Do NOT use for emotion commands directed at the device ("show sad", "be happy", bare "sad now"); those go through emotion/SKILL.md and are never logged here. Music/wellbeing skills consume the latest decision.
sensing-track
Query flow event logs to answer questions about past sensing events — "Have you seen anybody between 10pm and 12pm?", "Is there any motion in the last hour?", "What happened while I was away?".