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/fastrepl/anarlog/add-pluginnpx skills add fastrepl/anarlog --skill add-plugingit clone --depth 1 https://github.com/fastrepl/anarlogWhat 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.00059 | $0.00286 |
| Opus 5 | $0.00030 | $0.00143 |
| Sonnet 5 | $0.00012 | $0.00057 |
| Haiku 4.5 | $0.00006 | $0.00029 |
Grade A, and why
add-plugin 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.
What it actually says
Create a new plugin with:
npx @tauri-apps/cli plugin new NAME \
--no-example \
--directory ./plugins/NAME
Decide NAME from the user request, then run the generator.
Follow the style and conventions used in plugins/analytics:
- remove generated
rollup.config.js - remove generated
README.md - update
tsconfig.json - update
package.json
If the user does not ask for different command behavior, keep the single ping function in both ext.rs and commands.rs.
After the code changes are in place, generate bindings:
pnpm -F @anlg/plugin-<NAME> codegen
Finish by updating these integration points:
Cargo.tomlapps/desktop/src-tauri/Cargo.tomlapps/desktop/package.jsonapps/desktop/src-tauri/capabilities/default.json
Run pnpm i after updating apps/desktop/package.json.
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 · 41 lines · 59 tokens per session scan A 2d24ae65e174
add-plugin is a skill published in the GitHub repository fastrepl/anarlog (9,219 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 286 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
bug-triage
Use when triaging Phase Discord bug reports, syncing reports into triage artifacts, creating or updating GitHub issues, tracking bug clusters, or applying the repository's bug-fix review workflow.
oracle-parser
Use when doing any parser work — adding new Oracle text patterns, verb forms, phrase helpers, target patterns, subject handling, effect chain composition, fixing Unimplemented fallbacks, or understanding the parser architecture. This is the SINGLE SOURCE OF TRUTH for all oracle parser knowledge. Covers the nom…
pr-review-loop
Use to run a continuous review sweep over open contributor PRs in phase.rs. The skill is a thin orchestration layer over scripts/prreview.py: discover candidates, detect stale reviews/follow-ups, dispatch review-impl for PRs that need judgment, and delegate authorized merge handling to pr-contribution-handler.
add-ai-feature-policy
Use when adding a new deck-aware AI feature (DeckFeatures axis) and its companion policies (TacticalPolicy + optional MulliganPolicy) to phase-ai. Codifies the structural-detection pattern, AST-type locations, parts-based predicate convention, registry wiring sites, and recurring review traps so a new feature ships in…
engine-implementer
End-to-end phase.rs implementation pipeline: plan, review-plan, implement, review-impl, commit — each step run in a fresh spawned agent, with automatic phase decomposition for oversized workloads.
add-engine-effect
Use when adding a new effect, mechanic, or parser capability to the engine. Covers the full lifecycle from types → parser → resolver → targeting → frontend → AI → tests.