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 curie-eng/curie --skill factory-environment-maintenancegit clone --depth 1 https://github.com/curie-eng/curieWrote 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/curie-eng/curie/factory-environment-maintenance)<a href="https://agentmods.dev/skills/curie-eng/curie/factory-environment-maintenance"><img src="https://agentmods.dev/badge/skills/curie-eng/curie/factory-environment-maintenance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/curie-eng/curie/factory-environment-maintenance"><img src="https://agentmods.dev/badge/skills/curie-eng/curie/factory-environment-maintenance.svg" alt="Reviewed on agentmods" width="80" 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.00707 |
| Opus 5.5 | $0.00018 | $0.00283 |
| Sonnet 5.5 | $0.00009 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
factory-environment-maintenance 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain factory repository environments
Run on an admin-chosen schedule, such as weekly, and after a repeated failure cluster. The schedule invokes this local skill with the target factory and time window; the skill itself performs no background polling.
Read the configured factory bindings first. Treat each work item as a tracker issue plus a separate code-host repository; Jira issues may correspond to Bitbucket or GitHub pull requests. Use provider tools or APIs available to the operator for the actual binding. Do not assume GitHub labels, issue numbers, or PR URLs exist on every provider. GitHub uses issues and pull requests; GitLab uses issues and merge requests; Jira Cloud issues pair with the bound GitHub or Bitbucket Cloud/DC pull requests. Preserve each provider's immutable project and issue identity.
Review failures
- Read recent
curie cluster work-items --jsonoutcomes (or the local tier when appropriate), then inspect failed items and their tracker notices, run details, and code-host CI or review history. State the time window and count. The current work-items list is bounded; iftruncatedis true, continue through the provider's failure history when available and report any remaining coverage gap. Never claim to have examined all failures from a truncated page. Deduplicate retries of one root cause. An inaccessible record is unknown, not successful. - Group failures by cause and affected repository. Distinguish missing or wrong-version executables from blocked registry egress, unavailable services, credentials, sandbox capacity, CI/base health, publication restrictions, and incomplete task instructions. Correlate with the selected repository image digest and the exact failing command. Do not propose an image rebuild for a network-policy or credential failure.
- For an image cause, compare the operator-owned repository-runner spec with
the selected image's
/etc/curie/tool-manifest.json, then propose a catalog entry or custom Dockerfile/probe change. For other causes, name the owning configuration or ticket-preparation instruction and its administrator. Show affected examples, expected recurrence reduction, build or operational cost, a negative control, and rollback digest. Keep private evidence in a private admin record; use anonymous descriptions on public upstream surfaces. - Present a prioritized, reviewable set of changes. Do not modify a binding, push an image, widen egress, relabel issues, or retry work from this review alone. Approval of a specific candidate permits the setup skill's build, probe, sandbox validation, and deployment path. After deployment, compare new failures with the prior window and record whether the cause recurred.
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 · 57 lines · 46 tokens per session scan A 1a867c401174
factory-environment-maintenance is a skill published in the GitHub repository curie-eng/curie (46 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 707 once invoked, about $0.0002 per session on Opus 5.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-11-04.
factory-environment-maintenance compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| factory-environment-maintenancecurie-eng/curie | Skill | 46 | yesterday | Apache-2.0 | A | 46 | Claude Code |
| deployoliver-kriska/claude-elixir-phoenix | Skill | 574 | yesterday | MIT | A | 46 | Claude Code |
| relay-deploytonone-ai/tonone | Skill | 77 | 23d ago | MIT | A | 48 | Claude Code |
| devopsMindrally/skills | Skill | 297 | 29d ago | Apache-2.0 | A | 25 | Claude Code |
| relay-dockertonone-ai/tonone | Skill | 77 | 23d ago | MIT | A | 45 | Claude Code |
| ccc-devopsKevinZai/commander | Skill | 6 | yesterday | MIT | A | 42 | Claude Code |
| infra-standardsPrabhdeepSingh/claude-plugins | Skill | 4 | 10d ago | MIT | A | 106 | Claude Code |