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/buildrai/buildr/task-environmentnpx skills add BuildrAI/Buildr --skill task-environmentgit clone --depth 1 https://github.com/BuildrAI/BuildrWhat 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.00052 | $0.01954 |
| Opus 5 | $0.00026 | $0.00977 |
| Sonnet 5 | $0.00010 | $0.00391 |
| Haiku 4.5 | $0.00005 | $0.00195 |
Grade A, and why
task-environment 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 3d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Environment Skill
本 Skill 是 buildr.task-environment/v1 的默认 provider。它调用公开 CLI，不手写或解析 Environment Receipt。
Task Environment只拥有Buildr-managed checkout、Preparation、runtime projection、Task-owned持久资源、正式环境证据与cleanup authority。Formal Task Record、普通编辑、构建或有界测试本身不自动触发本Skill；缺少Plan/Receipt不能成为这些直接动作的通用许可blocker。直接工作不得反向补造Receipt或认领本Skill的ready、资源与cleanup结果。
开始行动时必须读取 references/project-environment-preparation-v1.md。只有经declaration-intake完成只读发现、展示精确diff，并形成routine-maintenance结论或取得长期适用性变化的用户授权后，才使用templates/project-preparation.yml维护长期声明；提交Task选择时使用 templates/task-environment-plan-request.json。不得绕过Intake分类、静默扩大scope、改变requiredness或把候选能力写入Project。
使用方式
必须已有正式 Task Record，并明确 canonical Workspace：
buildr task environment prepare <task-id> --agent <adapter> --target <canonical-workspace> --json
buildr task environment prepare <task-id> --plan <json-file> --agent <adapter> --target <canonical-workspace> --json
buildr task environment plan record --schema|--example --json
buildr task environment plan record <task-id> --input <json-file> --target <canonical-workspace> --json
buildr task environment plan inspect <task-id> --target <canonical-workspace> --json
buildr task environment inspect <task-id> --target <canonical-workspace> --json
buildr task environment cleanup <task-id> --target <canonical-workspace> --json
--agent对prepare必填，必须写成当前宿主，例如 Cursor 会话写cursor、Codex 会话写codex。不得省略，也不得假设省略后默认为 Codex。未给--branch时默认任务分支为<adapter>/<task-id>；显式--branch优先。- Project可选维护closed
preparation.yml，长期声明Project-wide或Service-scoped Recipe。Agent读取Task Record的完整Project/Service scope与构建、验证事实，并先用task environment plan record --schema|--example发现与实际normalizer同源的closed输入；只选择当前Task需要的Recipe，提交buildr.task-environment-plan-request/v1。Skill不得复制第二份schema或绕过Application的Task scope、declaration identity与Recipe ownership运行态校验；Application解析声明identity并保存buildr.task-environment-plan/v3执行快照。没有长期声明时可显式提交task-inlineRecipe，但不得静默回写Project。 - Formal Verification Plan preview或admission返回的closed
planRequest可以带auxiliaryPreparation。Agent只能原样交给本Skill的prepare --plan；它引用同Project已登记Recipe并绑定capability identity，不进入Task scope、Change、Content Target、allowed execution roots或源码写入authority。不得自行把辅助Service加入Task Record，也不得手写安装命令。 prepare --plan可一次完成登记与准备；若Agent必须先检查Task checkout，可先运行无Plan的prepare取得受控执行根（结果明确blocked），再运行plan record和prepare。- Plan Request只是CLI的一次性输入，不是Environment资源或长期事实。需要JSON文件时，Agent必须在操作系统临时目录创建，不得写入Workspace的
.buildr/tmp/、.buildr/transient/或其他受管资产目录；prepare --plan或plan record成功后必须立即删除。命令失败时，只有仍需用同一输入诊断或重试才能暂时保留，并必须报告路径；问题解决、放弃重试或Task终止后立即删除。 - Application保存的resolved
buildr.task-environment-plan/v3与buildr.task-environment-receipt/v6是Plan和机器状态authority；v3把Workspace path reference与executable authority分开，并把capability preparation closure与基础Task选择分开，v6保存closed runtime invocation与解析后的机器事实。旧Plan/Receipt只读；显式prepare --plan才升级。原始Plan Request不进入SQLite。Environment cleanup只清理Receipt已登记资源与provider-owned执行位置，不扫描或删除调用方临时输入。 prepare同时承担首次准备和幂等恢复；只重跑输出缺失或 executable/input identity 漂移的 Step，没有单独restore。inspect只读重新观察已保存Plan的executable、inputs和outputs；它不执行Step、不创建或修复输出、不回写Receipt。cleanup只在Task已明确abandon、Buildr已持久化并能重新验证Delivery evidence，或current Task Record为completed + noChange=true且provider证明checkout干净、HEAD未偏离Environment evidence时成立。Delivery可来自自动Finish或Agent直接交付后的reconciliation；Agent不提交claimed success，也不绕过ownership和Task Contribution等价检查。
What ships with it
4 files 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.
- 3d ago First seen · 57 lines · 52 tokens per session scan A 190ffa6469c5
task-environment is a skill published in the GitHub repository BuildrAI/Buildr (24 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 1,954 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…