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 commands/ll931217/dotfiles/setup-effectgit clone --depth 1 https://github.com/ll931217/dotfilesWhat 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.00017 | $0.01191 |
| Opus 5 | $0.00009 | $0.00596 |
| Sonnet 5 | $0.00003 | $0.00238 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
setup-effect 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Effect TypeScript setup guide. Your job is to help the user configure this repository to work brilliantly with Effect.
Tools
- Todo list: If available, use it to track progress. Create checklist at start, update as you complete steps. If no todo tool: show markdown checklist ONCE at start.
- AskUserQuestion: If available (Claude agents have this), use for multiple choice questions: package manager, project type, etc.
Confirmations: Ask before initializing a project, installing packages, modifying tsconfig, or creating/modifying agent files.
Before Starting
- Introduce yourself as their Effect setup guide
- Assess repository with a single command:
This finds all relevant files and detects symlinks. From lock file, determine package manager (bun/pnpm/npm). If multiple lock files, ask which to use. If none, ask preference.ls -la package.json tsconfig.json bun.lock pnpm-lock.yaml package-lock.json .vscode AGENTS.md CLAUDE.md .claude .cursorrules 2>/dev/null; file AGENTS.md CLAUDE.md 2>/dev/null | grep -i link - Check Effect Solutions CLI: run
effect-solutions list. If missing, install (using package nameeffect-solutions). If output shows update available, update before continuing. - Create todo list (if you have the tool)
Checklist:
- Initialize project (if needed)
- Install Effect dependencies
- Effect Language Service setup
- TypeScript compiler configuration
- Package scripts
- Agent instruction files
- Set up Effect source reference
- Summary
Initialize Project (if needed)
Only if package.json doesn't exist:
- Read:
effect-solutions show project-setup - Follow initialization guidance
- Run:
[bun/pnpm/npm] init
Install Effect Dependencies
- Check if Effect is already in dependencies
- Determine packages based on project type:
- Always:
effect - CLI apps:
@effect/cli - HTTP servers/clients:
@effect/platform
- Always:
- Schema lives in
effect/Schema; do not install@effect/schema(deprecated since Effect 3.10) - Run:
[bun/pnpm/npm] add effect [...] - Don't specify version - use latest
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 · 150 lines · 17 tokens per session scan A e214dff34663
setup-effect is a command published in the GitHub repository ll931217/dotfiles (21 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 1,191 once invoked, about $0.0001 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 commands, from other repositories
build-fix
빌드 에러를 자동으로 분석하고 수정합니다.
test-ts
Run TypeScript tests for Solana frontends and Anchor programs.
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
setup-project
Initialize a new Bun + TypeScript backend project with best practices setup (Hono, Prisma, Biome, testing, Docker).
sdk
Create or extract TypeScript SDK.
type-crusade
Unleash parallel TypeScript Purist agents to purge every any, as cast, and type sin across the codebase. No type sin survives.