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/vynazevedo/first-plan/lens-enginenpx skills add vynazevedo/first-plan --skill lens-enginegit clone --depth 1 https://github.com/vynazevedo/first-planWrote 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/vynazevedo/first-plan/lens-engine)<a href="https://agentmods.dev/skills/vynazevedo/first-plan/lens-engine"><img src="https://agentmods.dev/badge/skills/vynazevedo/first-plan/lens-engine.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.00070 | $0.01404 |
| Opus 5 | $0.00035 | $0.00702 |
| Sonnet 5 | $0.00014 | $0.00281 |
| Haiku 4.5 | $0.00007 | $0.00140 |
Grade A, and why
first-plan-lens-engine 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 6d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lens Engine
Motor que detecta stacks por manifesto, infere papel da pasta e roteia para a skill lens-<stack> correspondente.
Tabela de detecção (manifesto -> stack -> papel)
| Manifesto | Stack | Pistas adicionais para inferir papel |
|---|---|---|
go.mod |
Go | cmd/ = CLI/binário; internal/ = lib privada; pkg/ = lib pública; presença de chi/gin/echo/fiber = HTTP API; kafka-go/amqp/segmentio/kafka-go = consumer/producer |
package.json |
Node/TS | next.config.* = Next.js; vite.config.* = SPA Vite; nest-cli.json = NestJS; astro.config.* = Astro; remix.config.* = Remix; sveltekit em deps = SvelteKit; @nuxt/* = Nuxt; sem framework + bin/ = CLI Node |
composer.json |
PHP | artisan = Laravel; bin/console = Symfony; index.php em pasta public/ sem framework = legacy |
pyproject.toml / setup.py / requirements.txt |
Python | manage.py = Django; fastapi em deps = FastAPI; flask em deps = Flask; litestar = Litestar; celery em deps = worker; streamlit = data app |
Cargo.toml |
Rust | [[bin]] = binário; [lib] = lib; presença de actix-web/axum/rocket = HTTP API |
*.tf |
Terraform | main.tf na raiz = root módulo; modules/ = library; presença de provider "aws" etc para identificar plataforma |
Gemfile |
Ruby | config.ru = Rack; bin/rails = Rails; presença de sidekiq em Gemfile = worker |
pubspec.yaml |
Flutter / Dart | lib/main.dart = app Flutter; bin/ = CLI Dart |
Package.swift |
Swift | Sources/ = lib/app Swift |
build.gradle.kts ou build.gradle |
Kotlin/Java/Android | AndroidManifest.xml = Android app; application plugin = backend |
*.csproj ou *.sln |
.NET (C#) | <OutputType>Exe</> = CLI/web; Microsoft.AspNetCore = ASP.NET |
mix.exs |
Elixir | phoenix em deps = Phoenix |
deno.json ou deno.jsonc |
Deno | inferir papel pelo entry script |
bun.lockb ou bunfig.toml |
Bun | similar a Node/TS, framework por inspeção |
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.
- 6d ago First seen · 100 lines · 70 tokens per session scan A 053d8cfc136e
first-plan-lens-engine is a skill published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 11d ago), licensed MIT. It adds 70 tokens to every session and 1,404 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
agent-memory
Persistent memory system for AI coding agents. Use when you need to save facts about the user, store interaction preferences, log session events, or search previously saved memories. Triggers on remembering, saving context, recalling past decisions, or when the user says "remember this". Also use proactively when the…
snip
You are an expert at writing declarative YAML filters for snip, a CLI proxy that reduces LLM token consumption by filtering shell output.
release-notes
Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.
arch-check
架构与实现审查 —— 基于「概念建模 → 职责划分 → 机制/策略分离 → 因果与不变量 → 属性建模 → 模块化 → SOLID → GRASP → YAGNI」的全维度审查，带置信度门控与假阳性抑制（对抗"过度工程建议"这类 AI slop）。触发于：要求 review/审查架构、检查目录结构/依赖关系/职责划分、重构前评估、技术债盘点、判断是否过度设计，或问「这个设计合理吗 / 该怎么拆 / 有没有循环依赖 / 这个改动架构上 OK 吗」。一律按最高强度审查。用法：arch-check [范围] [--fix|--plan]。范围可为目录/文件/PR；缺省审当前分支相对基线的全部变更。.
Agent Context File Writer
Writes a high-quality CLAUDE.md, .cursorrules, or .windsurfrules file that gives a coding agent the right project context, conventions, and constraints to work effectively.
gh-merge
Completes the AgentsMesh GitHub pull-request workflow: commits scoped changes, rebases on the authoritative GitHub branch, opens or reuses a PR, monitors required checks, fixes failures, and merges only after verification. Use when the user asks to merge, submit, or land repository changes.