Borrowing it
Nothing to install: this file belongs to PacificStudio/openase. 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/PacificStudio/openase/main/.codex/skills/report-issue/SKILL.mdgit clone --depth 1 https://github.com/PacificStudio/openaseWrote 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/pacificstudio/openase/report-issue)<a href="https://agentmods.dev/skills/pacificstudio/openase/report-issue"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/report-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.
<a href="https://agentmods.dev/skills/pacificstudio/openase/report-issue"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/report-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.00596 |
| Opus 5.5 | $0.00024 | $0.00238 |
| Sonnet 5.5 | $0.00012 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
report-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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Issue
Goals
- Create a high-signal GitHub issue in the current repo.
- Optionally wire
blocked bydependencies before project binding. - Add it to project
OpenASE Automation(#2) with the requested status. - Default to
Todowhen the caller does not specify a status. - Keep issue bodies concrete: exact branch, commit, commands, actual result, expected result, impact, and likely fix direction.
Inputs To Collect
- Current branch:
git branch --show-current - Current commit:
git rev-parse HEAD - Relevant environment facts:
- deployment mode
- local ports
- whether
.envwas sourced - whether Docker/PostgreSQL was involved
- Exact repro command or API sequence
- Exact error text or log excerpt
Body Structure
Write issue bodies with these sections when applicable:
SummaryEnvironmentReproductionActual ResultExpected ResultLikely CauseImpactSuggested Fix Direction
Prefer exact commands and exact errors over paraphrase.
Workflow
- Gather concrete facts from the running repo and local deployment.
- Draft the issue body in a temp Markdown file.
- Create the issue with the helper script. The helper must run in this order:
- create issue
- add
blocked bydependencies, if any - add to project
- set project status
- Run:
.codex/skills/report-issue/scripts/create_issue_and_add_to_project.sh --title "<title>" --body-file <file> [--status "<status>"] [--blocked-by <issue-number> ...]
- Return the issue URL and confirm the actual project status that was set.
Supported --status values:
BacklogTodoIn ProgressReworkIn ReviewMergingDoneCanceledDuplicated
Notes
- Use one issue per distinct failure mode.
- Do not merge unrelated regressions into one issue.
- When a request includes multiple related tasks, create the parent and blocker issues first so later issues can reference them via
--blocked-by. - If the issue is a design task, explicitly state the desired contract and acceptance criteria.
- If the issue references PRD drift, say that PRD must be updated to remain the latest semantic source of truth.
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.
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.
- 1mo ago First seen · 82 lines · 60 tokens per session scan A cbfb86591a10
report-issue is a skill published in the GitHub repository PacificStudio/openase (269 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 596 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-08-30.
Other skills, from other repositories
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
meta-issue-to-pr-autopilot
Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.
meta-github-pr-watch-digest
Inspect the user's open GitHub PRs / failing CI / new issues via gh, summarize into 3 buckets (to-review / awaiting-me / CI-red), and persist follow-ups to memory.
omh-github-issue-intake
This is an OMH github-issue-intake workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.