configure

configure is a skill for Claude Code from piiiico/agentlair. It costs 46 tokens per session (797 once invoked), scanned A, original, MIT.

A setup command for an AgentLair email channel, including its API key, email address, and sender-access policy. AgentLair is the email service this channel connects to.

In plain words
What is it for?
Use it to save or inspect the AgentLair API key and address, review allowed senders, and check channel readiness.
Why use it?
It shows whether the channel is configured and guides the user through missing credentials or access settings.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Good fit Use it to save or inspect the AgentLair API key and address, review allowed senders, and check channel readiness.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/piiiico/agentlair/configure
Install

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.

Any agent
npx skills add piiiico/agentlair --skill configure
Clone the repo
git clone --depth 1 https://github.com/piiiico/agentlair

Made for: Claude Code.

Wrote 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.

agentmods badge for configure

README.md
[![agentmods](https://agentmods.dev/badge/skills/piiiico/agentlair/configure.svg)](https://agentmods.dev/skills/piiiico/agentlair/configure)
Your own site
<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>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 797 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 077f3ece0de5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 *)
apps/email-channel/skills/configure/SKILL.md · 83 lines

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:

  1. API Key — check ~/.claude/channels/agentlair-email/.env for AGENTLAIR_API_KEY. Show set/not-set; if set, show first 8 chars masked (al_live_...).

  2. Address — check for AGENTLAIR_ADDRESS in the same file. Show the full address if set.

  3. 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
  4. 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 allowlist to restrict access."
    • Both set, allowlist configured → "Ready. Only approved senders can reach you."

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

  1. 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
  2. mkdir -p ~/.claude/channels/agentlair-email
  3. Read existing .env if present; update/add the relevant lines, preserve other keys. Write back, no quotes around values.
  4. Confirm, then show the no-args status so the user sees where they stand.

Read the full file on GitHub · 83 lines

Changes

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.

  1. 8d ago First seen · 83 lines · 46 tokens per session scan A 077f3ece0de5

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens

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…

microsoft/vscode · 72 tokens