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/agirails/claude-plugin/agirails-securitynpx skills add agirails/claude-plugin --skill agirails-securitygit clone --depth 1 https://github.com/agirails/claude-pluginWhat 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.00052 | $0.01858 |
| Opus 5 | $0.00026 | $0.00929 |
| Sonnet 5 | $0.00010 | $0.00372 |
| Haiku 4.5 | $0.00005 | $0.00186 |
Grade A, and why
agirails-security 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGIRAILS Security Guide
Security is critical when handling payments. Follow these guidelines to protect user funds and maintain trust.
Key Resolution Order
The SDK resolves signing keys in this priority:
1. ACTP_PRIVATE_KEY env var (explicit key, for CI/testing)
2. .actp/keystore.json + ACTP_KEY_PASSWORD (encrypted at rest, recommended)
3. wallet: 'auto' (Smart Wallet + micro-airdrop gas, zero-config)
The address is always derived from the key automatically -- never specify requesterAddress manually.
Critical Security Rules
1. Never Hardcode Private Keys
// WRONG - Private key exposed in code
const client = await ACTPClient.create({
mode: 'mainnet',
privateKey: '0x1234567890abcdef...', // CRITICAL BUG
});
// CORRECT - SDK auto-detects from keystore
const client = await ACTPClient.create({ mode: 'mainnet' });
// Key loaded from .actp/keystore.json + ACTP_KEY_PASSWORD env var
2. Never Log Sensitive Data
// WRONG - Key could appear in logs
console.log('Initializing with key:', privateKey);
logger.debug({ privateKey, address });
// CORRECT - Never log keys
console.log('Initializing wallet:', address);
logger.debug({ address, mode });
3. Always Use .gitignore
# AGIRAILS
.actp/
.env
.env.local
.env.*.local
4. Validate All Inputs
// WRONG - No validation
async function pay(to: string, amount: string) {
return client.basic.pay({ to, amount });
}
// CORRECT - Validate inputs
async function pay(to: string, amount: string) {
if (!isValidAddress(to)) {
throw new Error('Invalid address');
}
if (!isValidAmount(amount)) {
throw new Error('Invalid amount');
}
if (to.toLowerCase() === myAddress.toLowerCase()) {
throw new Error('Cannot pay yourself');
}
return client.basic.pay({ to, amount });
}
Key Management
Development (Mock Mode)
No key needed -- mock mode generates ephemeral keys:
const client = await ACTPClient.create({ mode: 'mock' });
What ships with it
2 files 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 · 279 lines · 52 tokens per session scan A 85006c125f25
agirails-security is a skill published in the GitHub repository agirails/claude-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,858 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…