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/auditnpx skills add nodealchemy/powernode-platform --skill auditgit 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.00011 | $0.00774 |
| Opus 5 | $0.00005 | $0.00387 |
| Sonnet 5 | $0.00002 | $0.00155 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
audit 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Quality Audit
Run quality checks and report results. Accept an optional focus argument to limit scope.
Focus Areas
- all (default) — run everything
- backend — Ruby checks only (steps 1, 4, 5, 6)
- frontend — Frontend checks only (steps 3, 7, 8)
- types — TypeScript type check only (step 3)
- patterns — Pattern validation only (steps 1, 2)
Checks
Run applicable checks sequentially. Capture output from each.
1. Pattern Validation
cd $PROJECT_DIR && ./scripts/pattern-validation.sh
2. Quick Pattern Check
cd $PROJECT_DIR && ./scripts/quick-pattern-check.sh
3. TypeScript Type Check
cd $PROJECT_DIR/frontend && npx tsc --noEmit 2>&1
4. Ruby Syntax Check
Check all .rb files changed since last commit:
cd $PROJECT_DIR/server && git diff --name-only HEAD -- '*.rb' | xargs -I{} ruby -c {} 2>&1
Also check untracked .rb files:
cd $PROJECT_DIR/server && git ls-files --others --exclude-standard -- '*.rb' | xargs -I{} ruby -c {} 2>&1
5. Rails Eager Load Check (backend only)
Verify all Ruby classes load without errors:
cd $PROJECT_DIR/server && bundle exec rails runner "Rails.application.eager_load!; puts 'Eager load OK'" 2>&1
6. Frozen String Literal Pragma
Scan for Ruby files missing the pragma:
grep -rL "frozen_string_literal: true" $PROJECT_DIR/server/app/ --include="*.rb" | head -20
7. Console.log Scan
grep -rn "console\.log" $PROJECT_DIR/frontend/src/ --include="*.ts" --include="*.tsx" | head -20
8. Hardcoded Color Scan
grep -rn "bg-\(red\|blue\|green\|yellow\|gray\|slate\|zinc\|neutral\|stone\)" $PROJECT_DIR/frontend/src/ --include="*.tsx" | grep -v "theme" | head -20
Output
Present results as a summary table:
| Check | Status | Issues |
|------------------------|--------|--------|
| Pattern Validation | ✅/❌ | count |
| Quick Pattern Check | ✅/❌ | count |
| TypeScript Types | ✅/❌ | count |
| Ruby Syntax | ✅/❌ | count |
| Rails Eager Load | ✅/❌ | count |
| Frozen String Literal | ✅/❌ | count |
| Console.log | ✅/❌ | count |
| Hardcoded Colors | ✅/❌ | count |
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 · 90 lines · 11 tokens per session scan A cf79fa897367
audit is a skill published in the GitHub repository nodealchemy/powernode-platform (2 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 774 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).