Install
$ agentstack add skill-furkantokkan-agent-foundry-bug-report ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Bug Report
Codex port of Claude Code Game Studios /bug-report.
Use this skill when the task matches the workflow described below. Keep the Codex version lightweight: load references/claude-skill.md only when the original detailed Claude workflow is needed.
Codex Workflow
- Read repository-local instructions first:
AGENTS.md,CLAUDE.md, the
nearest path-scoped instructions (Assets/CLAUDE.md for Unity when present), and any referenced project docs.
- Use this workflow's intent, but follow Codex tool and collaboration rules.
- Apply SOLID, Clean Code, clear English naming, dependency boundaries, and
focused tests for new or changed expected behavior.
- When a Claude workflow mentions a custom agent, treat it as a role reference.
Do the work locally unless the user explicitly asks for sub-agents or parallel agent work.
- For implementation tasks, make the change directly when the request is clear;
ask only when a decision cannot be safely inferred from local context.
- Verify with the repository's available checks and summarize changed files,
tests run, and residual risk.
Before filing production/qa/bugs/BUG-*.md, search tracked task contracts by exact ID and by objective, acceptance, preserved behavior, and managed defect ledger. A failure of an existing task's acceptance/preservation or a regression caused by that task must be forwarded internally to $task-bug [] ""; do not create a standalone QA bug file. task-bug resolves the owner and task-cycle is the sole writer of linked same-task defect records and ledger state. Ask one identity question only when several task contracts plausibly own the observation. Continue the standalone report workflow only for an unrelated pre-existing defect or a bug without a tracked task owner, and only when the operator is intentionally capturing/triaging a backlog report. If the operator requested a bounded repair instead, stop NO_TASK_MATCH and suggest $create-task ""; do not silently replace repair execution with a QA report.
Original Workflow Summary
Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.
Detailed Reference
- Original Claude skill:
references/claude-skill.md
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: furkantokkan
- Source: furkantokkan/agent-foundry
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.