Borrowing it
Nothing to install: this file belongs to c9r-io/orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/c9r-io/orchestrator/main/.claude/skills/reset-local-env/SKILL.mdgit clone --depth 1 https://github.com/c9r-io/orchestratorWrote 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/c9r-io/orchestrator/reset-local-env)<a href="https://agentmods.dev/skills/c9r-io/orchestrator/reset-local-env"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/reset-local-env/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/c9r-io/orchestrator/reset-local-env"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/reset-local-env.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.00036 | $0.00377 |
| Opus 5 | $0.00018 | $0.00188 |
| Sonnet 5 | $0.00007 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
reset-local-env 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 9d 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.
What it actually says
Reset Local Environment
Reset is destructive. Resolve the exact state boundary first and preserve unrelated projects, tickets, and in-flight tasks.
Agent Orchestrator Repository
This repository has no Docker Compose reset contract. For isolated QA state, prefer the product-owned project boundary:
orchestrator delete project/<project> --force
orchestrator apply -f fixtures/manifests/bundles/<fixture>.yaml --project <project>
Before deletion, list tasks for the target project and confirm the project name. Do not delete ~/.orchestratord/, its SQLite database, or tracked files in docs/ticket/ as a routine reset.
If the database is missing, orchestrator init creates runtime state. It is not a reset command.
Generated Project Docker Branch
Only a target generated by project-bootstrap is expected to carry scripts/reset-docker.sh and docker/docker-compose.yml. Require both paths and preview the script before running it:
test -x scripts/reset-docker.sh
test -f docker/docker-compose.yml
sed -n '1,240p' scripts/reset-docker.sh
Then state explicitly that containers, project images, and volumes will be replaced. Run the repository-owned script only after the user-authorized target and data loss boundary are clear.
Verification
- Agent Orchestrator: re-apply the exact mock fixture, create one bounded test task, and inspect it through the CLI.
- Generated Docker project: confirm Compose services and health checks declared by its compose file.
- Report what was removed and whether recovery is possible.
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.
- 9d ago First seen · 40 lines · 36 tokens per session scan A 003505b45b56
reset-local-env is a skill published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 377 once invoked, about $0.0002 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
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.