Borrowing it
Nothing to install: this file belongs to P2ERGmbH/agentic-coding. 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/P2ERGmbH/agentic-coding/main/.agents/skills/github-issue-test/SKILL.mdgit clone --depth 1 https://github.com/P2ERGmbH/agentic-codingWrote 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/p2ergmbh/agentic-coding/github-issue-test)<a href="https://agentmods.dev/skills/p2ergmbh/agentic-coding/github-issue-test"><img src="https://agentmods.dev/badge/skills/p2ergmbh/agentic-coding/github-issue-test/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/p2ergmbh/agentic-coding/github-issue-test"><img src="https://agentmods.dev/badge/skills/p2ergmbh/agentic-coding/github-issue-test.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.00019 | $0.01984 |
| Opus 5.5 | $0.00008 | $0.00794 |
| Sonnet 5.5 | $0.00004 | $0.00397 |
| Haiku 4.5 | $0.00002 | $0.00198 |
Grade A, and why
github-issue-test 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 2mo 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Verification Workflow
This workflow guides you through standardizing the verification of implemented GitHub issues on the development environment.
Role & Persona
You are an expert software engineer and autonomous agent.
Trigger
Use this workflow whenever the user asks to "run the github-issue-test workflow," "verify issue #," or "test if issue # is resolved."
Phase 1: Issue Analysis and State Detection
- Fetch Issue Details:
- Use the
get_issuetool to fetch the details of the target issue (referred to as$ISSUE_NUMBER).
- Use the
- Verify Implementation State:
- Use
search_issueswith a query likerepo:your-org/your-repo is:pr $ISSUE_NUMBERto find associated Pull Requests. - Verify that at least one linked Pull Request has been merged.
- If no merged PR is found, notify the user that the issue might not be deployed yet and ask if you should proceed.
- Use
- Extract the Test Case:
- Identify the "Browser Click Path" or "Acceptance Criteria" from the issue description.
- If no click path is explicitly defined, infer one based on the implemented features.
- Environment Detection:
- If the resolving PR is merged, verify on the development environment:
https://dev.your-domain.com. - If the PR is NOT merged, run the test on the local development server:
http://localhost:6767.
- If the resolving PR is merged, verify on the development environment:
Phase 2: Test Plan Preparation
- Translate Paths:
- All relative paths and localhost URLs must be translated to the correct environment base:
https://dev.your-domain.com/orhttp://localhost:6767/. - Crucial: Ensure you explicitly use the
/de/locale (or the required locale) in the URL to maintain environment parity (e.g.,https://dev.your-domain.com/de/dashboard). - Redirect Strategy: Instead of manual click-through, you can append the
?to=parameter on the login page to navigate directly to the target page after authentication (e.g.,https://dev.your-domain.com/de/login?to=provider/item-1/settings). Make sure thetoparameter does NOT include the locale prefix.
- All relative paths and localhost URLs must be translated to the correct environment base:
- Retrieve Test Credentials:
- Read the centralized verification file at
docs/test/smoke-test.mdto locate the correct test account for your scenario. - The default Chrome DevTools credential is
[email protected]with the common password documented in that file.
- Read the centralized verification file at
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.
- 2mo ago First seen · 125 lines · 19 tokens per session scan A e148ecc060e5
github-issue-test is a skill published in the GitHub repository P2ERGmbH/agentic-coding (9 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 1,984 once invoked, about $0.0001 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-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.