Waku Agent is a local-first personal AI assistant whose readable code implements the agent loop, memory, and evaluation system. It is for people who want an assistant they can run and understand on their own laptop, with memory stored in SQLite and built-in testing. The catalogue add-ons support its agent workflow.
Borrowing it
Nothing to install: this file belongs to ShenSeanChen/waku-agent. 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/ShenSeanChen/waku-agent/main/.claude/skills/pr-worktree/SKILL.mdgit clone --depth 1 https://github.com/ShenSeanChen/waku-agentWrote 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/shenseanchen/waku-agent/pr-worktree)<a href="https://agentmods.dev/skills/shenseanchen/waku-agent/pr-worktree"><img src="https://agentmods.dev/badge/skills/shenseanchen/waku-agent/pr-worktree/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/shenseanchen/waku-agent/pr-worktree"><img src="https://agentmods.dev/badge/skills/shenseanchen/waku-agent/pr-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 34 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 50 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 82 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 90 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 98 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00056 | $0.01070 |
| Opus 5 | $0.00028 | $0.00535 |
| Sonnet 5 | $0.00011 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade C, and why
pr-worktree scanned grade C with 1 finding 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 9d 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.
Enumerates the file system for secretshighData exfiltration
Searching home directories for .env, .ssh, .aws or credential files is reconnaissance for credential theft.
find ~/Developer/waku-prs -name ".env" 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Throwaway worktrees for PR testing
Testing a contributor's PR must never disturb the live dashboard on 7777, and it must never leave a second copy of Sean's API keys on disk. Both have happened.
Setting one up
REPO=$(git rev-parse --show-toplevel)
N=<pr-number>
git -C $REPO fetch -q origin pull/$N/head:pr-$N
git -C $REPO worktree add -q ~/Developer/waku-prs/pr$N pr-$N
ln -sfn $REPO/.waku ~/Developer/waku-prs/pr$N/.waku # real memory/traces/calendar
Never gh pr checkout — it switches the branch of the main working tree, and the
live dashboard runs from there.
Only link .env when the test actually needs keys
Deterministic evals do not. Skip the symlink for a test-only pass, so untrusted contributor code never runs against real credentials. Link it only after you have read the diff:
ln -sfn $REPO/.env ~/Developer/waku-prs/pr$N/.env
The symlink trap (this cost us a full copy of every key)
python-dotenv's set_key — which the dashboard's Save & switch calls —
replaces a symlinked .env with a regular file. The moment anyone saves a
setting from a PR worktree's dashboard, that worktree gains a complete copy of
every key in the real .env: Anthropic, OpenAI, Gemini, Moonshot, xAI, Zhipu,
Tavily, Telegram, Discord.
So: after any test that saved settings, assume the .env is a real file and
check before deleting the worktree, then move anything worth keeping into the
main .env rather than losing it.
[ -L ~/Developer/waku-prs/pr$N/.env ] && echo "symlink (safe)" || echo "REAL FILE — copy of all keys"
New env vars a PR introduces belong in the main .env, not the worktree's.
Copy the values across without printing them, and leave switches that would change
what the live demo shows (e.g. WAKU_EPISODIC_STORE) on their old value — Sean
films against the local data.
Running its dashboard
Always a second port, so 7777 stays untouched:
cd ~/Developer/waku-prs/pr$N
WAKU_DASHBOARD_PORT=7778 $REPO/.venv/bin/python -m waku.ops.dashboard
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.
- 9d ago First seen · 105 lines · 56 tokens per session scan C 17b37c91797c
pr-worktree is a skill published in the GitHub repository ShenSeanChen/waku-agent (1,696 stars, last pushed 11d ago), licensed MIT. It adds 56 tokens to every session and 1,070 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (enumerates the file system for secrets). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
github-auth
Set up GitHub authentication for the agent using git (universally available) or the gh CLI. Covers HTTPS tokens, SSH keys, credential helpers, and gh auth — with a detection flow to pick the right method automatically.
git-expert
Git operations expert for branching, rebasing, conflicts, and workflows.
github
GitHub operations expert for PRs, issues, code review, Actions, and gh CLI.
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
update-recovery
A procedure for recovering custom changes after an Iva software update creates conflicts between the old and new versions.