report-environment-issue

report-environment-issue is a skill for Claude Code, Codex from DasDigitaleMomentum/opencode-processing-skills. It costs 38 tokens per session (709 once invoked), scanned A, original, MIT.

A skill for recording environment and tooling problems in an append-only log, while avoiding duplicate entries. It covers issues such as missing tools, permissions, network restrictions, and unreliable providers.

In plain words
What is it for?
Use it when an agent is blocked or slowed by a sandbox, credential, installer, MCP, browser, model, or other runtime problem.
Why use it?
It separates problems caused by the development environment from bugs in the product code, making recurring setup failures easier to track and improve.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions OpenCode.

Good fit Use it when an agent is blocked or slowed by a sandbox, credential, installer, MCP, browser, model, or other runtime problem.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dasdigitalemomentum/opencode-processing-skills/report-environment-issue
Install

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.

Any agent
npx skills add DasDigitaleMomentum/opencode-processing-skills --skill report-environment-issue
Clone the repo
git clone --depth 1 https://github.com/DasDigitaleMomentum/opencode-processing-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for report-environment-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/report-environment-issue/github.svg)](https://agentmods.dev/skills/dasdigitalemomentum/opencode-processing-skills/report-environment-issue)
Your own site
<a href="https://agentmods.dev/skills/dasdigitalemomentum/opencode-processing-skills/report-environment-issue"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/report-environment-issue/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.

agentmods 80×15 button for report-environment-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/dasdigitalemomentum/opencode-processing-skills/report-environment-issue"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/report-environment-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 709 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.00709
Opus 5.5 $0.00015 $0.00284
Sonnet 5.5 $0.00008 $0.00142
Haiku 4.5 $0.00004 $0.00071

Measured 1mo ago against content hash 1f5aa0ec6c5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

report-environment-issue 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 1mo 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.

skills/report-environment-issue/SKILL.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Report Environment Issue

Capture issues that are outside the current work package's control, so recurring environment friction becomes visible and can be improved over time.

When to Use

Use when work is blocked or degraded by the environment rather than by the product code or gated scope, for example:

  • missing tool, binary, permission, or credential
  • sandbox, network, proxy, or filesystem restriction
  • installer, path, symlink, or harness configuration problem
  • tool, MCP, or browser provider failure or flakiness
  • provider, model, or runtime constraint

Do not use for product bugs, review findings, plan changes, or user-owned decisions. Those keep their own workflows.

Execution Model

  • The Maintainer records issues it observed directly or that a subagent reported in its return or digest.
  • doc-explorer may maintain the log when routed for bulk curation or deduplication cleanup.
  • Subagents do not write the log; they surface a compact Environment: <category>: <symptom> note in their return.

Workflow

  1. Decide whether the issue is environmental (outside the work package's control) and whether it is fixable now.
    • Fixable within the current package and scope → fix it; do not log it.
    • Not fixable now → record it here.
  2. Read docs/environment-issues.md if it exists; otherwise create it from tpl-environment-issues.md.
  3. Match an existing entry by category plus normalized symptom.
    • Match → increment occurrences, update last seen, adjust status or workaround if changed, and append a history line.
    • No match → assign the next ENV-NNN ID and add both a summary row and an entry.
  4. Keep entries short and evidence-based. Never invent a cause; record the exact symptom and the observed workaround.
  5. Report the recorded ID back to the user or main loop.

Output Contract

Return only:

  • Recorded: ENV-NNN (new) | ENV-NNN (updated) | none
  • File: docs/environment-issues.md
  • Summary: one line: category + symptom
  • Next: stop | primary decision required

Read the full file on GitHub · 74 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 1mo ago First seen · 74 lines · 38 tokens per session scan A 1f5aa0ec6c5f

Subscribe to this mod's changes

report-environment-issue is a skill published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (60 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 709 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-09-10.