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/nodealchemy/powernode-platform/fix-testsnpx skills add nodealchemy/powernode-platform --skill fix-testsgit clone --depth 1 https://github.com/nodealchemy/powernode-platformWhat 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.00015 | $0.00681 |
| Opus 5 | $0.00008 | $0.00341 |
| Sonnet 5 | $0.00003 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
fix-tests 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 yesterday.
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Tests Workflow
Run the test suite for the given scope, diagnose failures, fix them, and re-run. Follow this process exactly:
Step 1: Determine Scope & Mode
Parse the argument to determine what to run:
backendor no argument →cd server && bundle exec rspec --format progressfrontend→cd frontend && CI=true npm teste2e→cd frontend && npx playwright test- A specific file path → run that file directly
Loop mode (--loop): Run the full fix cycle autonomously without asking for input. Make best-judgment fixes. Suitable for headless/unattended runs via claude -p "/fix-tests backend --loop".
Step 2: Run Tests
Execute the test command and capture output. Note all failures.
Step 3: Fix Loop (max 3 attempts per failure)
For each failing test:
- Read the failing spec file and the source file it tests
- Diagnose the root cause — check for:
- Missing factory traits (check
spec/factories/andspec/factories/ai/) - Wrong test helpers (use
user_with_permissions,auth_headers_for,json_response) - Missing shared examples (
spec/support/shared_examples/) - Missing mocks or stubs for external services
- Stale selectors in E2E tests (prefer
data-testid) - Import path issues (use
@/shared/,@/features/)
- Missing factory traits (check
- Fix the issue using Edit
- Re-run just the failing file to verify the fix
- If still failing after 3 attempts on the same test, stop and report — do not keep iterating
Step 4: TypeScript Check (frontend/e2e only)
If any TypeScript files were modified:
cd frontend && npx tsc --noEmit
Fix any type errors found (same 3-attempt limit).
Step 5: Final Run
Re-run the full suite for the original scope to confirm everything passes.
Step 6: Loop Mode Continuation (--loop only)
If --loop flag was provided and Step 5 still has failures:
- Return to Step 3 with the NEW set of failures (not the originals)
- Repeat the full cycle up to 3 total loop iterations
- If failures persist after 3 full loops, stop and report
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.
- yesterday First seen · 72 lines · 0 tokens per session scan A a27c075b62b1
fix-tests is a skill published in the GitHub repository nodealchemy/powernode-platform (2 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 681 once invoked, about $0.0001 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 skills, from other repositories
good-first-issue-batch
File a batch of contributor-ready GitHub issues from the seeds backlog, re-verifying every candidate against HEAD first so no dead issue reaches a contributor. Activate for prompts like "file some good first issues", "open a batch of GFIs", "publish backlog issues to GitHub", "find contributor-ready work", or after an…
seeds-issue-audit
Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases. Activate for prompts like "audit open issues", "which seeds issues can be closed", "clean up the issue tracker", "triage the seeds backlog".
os-eco-dep-sync
Bump warren onto the latest published @os-eco/ versions across package.json + bun.lock and the Dockerfile CLI pins, then run the gates and open a PR. Use when checking if warren is on the newest burrow/plot/canopy/seeds/mulch/sapling.
release
Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.
warren-dogfood-pipeline
Full prioritize → dispatch → shepherd → track pipeline against the live warren instance. Audits the seeds backlog around a focus theme, dispatches the surviving issues to warren agents one at a time, babysits the resulting PRs to merge (update-branch, conflict-repair runs, auto-merge), and closes the loop in the…
canvas
Display HTML content on connected Mayros nodes (Mac app, iOS, Android).