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 piiiico/agentlair --skill configuregit clone --depth 1 https://github.com/piiiico/agentlairWrote 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/piiiico/agentlair/configure)<a href="https://agentmods.dev/skills/piiiico/agentlair/configure"><img src="https://agentmods.dev/badge/skills/piiiico/agentlair/configure.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.00046 | $0.00797 |
| Opus 5 | $0.00023 | $0.00398 |
| Sonnet 5 | $0.00009 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
configure scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Bash(curl *) How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/agentlair-email:configure — AgentLair Email Channel Setup
Writes credentials to ~/.claude/channels/agentlair-email/.env and orients
the user on access policy. The server reads both files at boot.
Arguments passed: $ARGUMENTS
Dispatch on arguments
No args — status and guidance
Read both state files and give the user a complete picture:
-
API Key — check
~/.claude/channels/agentlair-email/.envforAGENTLAIR_API_KEY. Show set/not-set; if set, show first 8 chars masked (al_live_...). -
Address — check for
AGENTLAIR_ADDRESSin the same file. Show the full address if set. -
Access — read
~/.claude/channels/agentlair-email/access.json(missing file = defaults:policy: "open", empty allowlist). Show:- Policy and what it means in one line
- Allowed senders: count and list
-
What next — end with a concrete next step based on state:
- No API key → "Run
/agentlair-email:configure <api-key> <address>to set up. Get an API key at https://agentlair.dev/dashboard." - Key set, no address → "Run
/agentlair-email:configure --address [email protected]to set the monitoring address." - Both set, policy is open → "Ready. Anyone who knows your address can
email you. Run
/agentlair-email:access policy allowlistto restrict access." - Both set, allowlist configured → "Ready. Only approved senders can reach you."
- No API key → "Run
Push toward lockdown — always. Open policy is convenient but a prompt injection risk. Once setup is complete, suggest switching to allowlist.
<api-key> or <api-key> <address> — save credentials
- Parse
$ARGUMENTS:- If one arg starting with
al_→ API key only - If two args → first is API key, second is address
- If arg contains
@agentlair.dev→ address only
- If one arg starting with
mkdir -p ~/.claude/channels/agentlair-email- Read existing
.envif present; update/add the relevant lines, preserve other keys. Write back, no quotes around values. - Confirm, then show the no-args status so the user sees where they stand.
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 · 83 lines · 46 tokens per session scan A 077f3ece0de5
configure is a skill published in the GitHub repository piiiico/agentlair (3 stars, last pushed 17d ago), licensed MIT. It adds 46 tokens to every session and 797 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…