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 skills add Kasempiternal/Claude-Agent-System --skill l30git clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote 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/kasempiternal/claude-agent-system/l30)<a href="https://agentmods.dev/skills/kasempiternal/claude-agent-system/l30"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/l30.svg" alt="Measured on agentmods" height="20"></a>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.00059 | $0.03718 |
| Opus 5 | $0.00030 | $0.01859 |
| Sonnet 5 | $0.00012 | $0.00744 |
| Haiku 4.5 | $0.00006 | $0.00372 |
Grade A, and why
l30 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 8d 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
██╗ ██████╗ ██████╗
██║ ╚════██╗██╔═████╗
██║ █████╔╝██║██╔██║
██║ ╚═══██╗████╔╝██║
███████╗ ██████╔╝╚██████╔╝
╚══════╝ ╚═════╝ ╚═════╝
Topic Research • Last 30 Days
CLAUDE AGENT SYSTEM
MANDATORY: Output the banner above verbatim as your very first message to the user, before any tool calls or other output.
You are entering L30 RESEARCH MODE. You deploy a parallel agent swarm that scrapes 5 free sources (Reddit, Hacker News, DuckDuckGo, Lobsters, GitHub) using Scrapling, scores and ranks the results, then generates a self-contained HTML dashboard.
Your Role: Swarm Orchestrator
- Parse the user's topic from
$ARGUMENTS - Create a team and task graph with dependencies
- Spawn 5 parallel scraper agents (Wave 1)
- Spawn an intelligence agent to score/rank/deduplicate (Wave 2)
- Spawn a report compiler to generate the HTML dashboard (Wave 3)
- Show a summary and open the dashboard
Phase 0: Prerequisites
Step 1: Locate Skill Directory
Use Glob("**/skills/l30/templates/dashboard.html") to find the dashboard template. Extract the parent directory path (everything before /templates/). Store as L30_SKILL_DIR.
Step 2: Verify Python Environment
Resolve L30_PYTHON in this order:
- If
$L30_PYTHONis set, use that interpreter. - Otherwise, if
$L30_HOMEis set, use$L30_HOME/.venv/bin/python. - Otherwise, use
python3found onPATH.
L30_HOME must be the l30 project directory. To configure a project-local environment in one step:
cd <l30-project-directory> && python3 -m venv .venv && .venv/bin/pip install -e .
Then set L30_HOME=<l30-project-directory> or L30_PYTHON=<path-to-python> before invoking /l30.
Run a Bash command that resolves the interpreter in that order and verifies it:
if [ -n "${L30_PYTHON:-}" ]; then
VENV="$L30_PYTHON"
elif [ -n "${L30_HOME:-}" ]; then
VENV="$L30_HOME/.venv/bin/python"
else
VENV="$(command -v python3 || true)"
fi
test -n "$VENV" && test -x "$VENV" && "$VENV" -c 'import l30' && printf '%s\n' "$VENV"
What ships with it
1 file 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.
- 8d ago First seen · 371 lines · 59 tokens per session scan A 49dd33b325e4
l30 is a skill published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 3,718 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
project-setup
Classify, plan, reconcile, and bootstrap software product repositories. Use this skill when starting a greenfield web, SaaS, desktop, mobile, API, CLI, SDK, developer-tool, data, AI, browser-extension, or hybrid product; when scanning an existing repository before adopting it; or when creating or repairing product…
credential-setup-with-computer-use
Guides n8n credential setup through Computer Use browser tools. Use when a user needs OAuth apps, API keys, client IDs, client secrets, or other credential values from an external service console.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.