What is report-issue?

A routine for creating a detailed GitHub issue, a tracked report or task in a code repository, and adding it to the OpenASE Automation project.

Recording the branch, commit, environment, reproduction steps, actual and expected results, impact, likely cause, and suggested fix direction.

It turns a bug or design request into reproducible evidence that others can investigate, prioritize, and track.

report-issue — Skill for Claude Code and Codex by PacificStudio: A routine for creating a detailed GitHub issue, a…

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.

agentmods

npx agentmods add skills/pacificstudio/openase/report-issue

Any agent

npx skills add PacificStudio/openase --skill report-issue

Clone the repo

git clone --depth 1 https://github.com/PacificStudio/openase

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pacificstudio/openase/report-issue.svg)](https://agentmods.dev/skills/pacificstudio/openase/report-issue)

Your own site

<a href="https://agentmods.dev/skills/pacificstudio/openase/report-issue"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/report-issue.svg" alt="Measured on agentmods" height="20"></a>

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 596 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00060	$0.00596
Opus 5	$0.00030	$0.00298
Sonnet 5	$0.00012	$0.00119
Haiku 4.5	$0.00006	$0.00060

Measured 3d ago against content hash cbfb86591a10, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/create_issue_and_add_to_project.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.codex/skills/report-issue/SKILL.md · 82 lines

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 by dependencies before project binding.
Add it to project OpenASE Automation (#2) with the requested status.
Default to Todo when 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 .env was 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:

Summary
Environment
Reproduction
Actual Result
Expected Result
Likely Cause
Impact
Suggested 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 by dependencies, 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:

Backlog
Todo
In Progress
Rework
In Review
Merging
Done
Canceled
Duplicated

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.

Read the full file on GitHub · 82 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.

scripts/create_issue_and_add_to_project.sh 4.2 KB runs code

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.

3d ago First seen · 82 lines · 60 tokens per session scan A cbfb86591a10

Subscribe to this mod's changes

report-issue is a skill published in the GitHub repository PacificStudio/openase (265 stars, last pushed 25d ago), licensed Apache-2.0. It adds 60 tokens to every session and 596 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.

Git and workflow Project management agent ai software-engineering

aisee:init

初始化、审计并优化 OpenSpec/Aisee 项目配置。仅适用于已使用或准备接入 OpenSpec 的项目；用于创建或修复 AGENTS.md、openspec/project.md、aisee/memory/、最小 Aisee docs 目录，并在当前支持的 Codex hook target 下安装项目级 hooks；检查 hook 机制兼容性、OpenSpec 状态机、baseline 迁移入口与项目技术架构边界。触发词包括 aisee:init、aisee-init、初始化项目配置、优化 AGENTS.md、配置 Codex hooks、OpenSpec 配置审计。.

AISEE-LAB/aisee-plugin · 134 tokens

aisee:srs

通过结构化对话充分澄清软件类业务需求，并生成规划级详细的需求规格说明书（SRS）。当用户想写需求文档、澄清产品范围、整理业务目标/用户角色/业务能力/业务流程/业务规则/权限/非目标，或为 aisee:change-plan 准备稳定输入时使用。适用于 App、小程序、Web、桌面软件、后端/API 服务、CLI 工具、定时任务/异步任务等软件项目。SRS 应写到足够支持后续拆 change 和编写 change 内容，但不要写成接口设计、数据库设计、技术方案、视觉设计、硬件架构、固件设计或开发任务。.

AISEE-LAB/aisee-plugin · 159 tokens

report-issue