A helper that turns a free-text description into a structured GitHub issue and posts it to a repository. A GitHub issue is a tracked report or task for a project.

Use it to file a clearly described bug or task, with a title, body, labels, and optional context from the codebase.

It saves time formatting the report and adds safeguards against publishing confidential information in a public repository.

How bayesimpact/bayes-platform configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bayesimpact/bayes-platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bayesimpact/bayes-platform/main/.claude/skills/new-issue/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/bayesimpact/bayes-platform

Made for: Claude Code.

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/bayesimpact/bayes-platform/new-issue/github.svg)](https://agentmods.dev/skills/bayesimpact/bayes-platform/new-issue)

Your own site

<a href="https://agentmods.dev/skills/bayesimpact/bayes-platform/new-issue"><img src="https://agentmods.dev/badge/skills/bayesimpact/bayes-platform/new-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bayesimpact/bayes-platform/new-issue"><img src="https://agentmods.dev/badge/skills/bayesimpact/bayes-platform/new-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,620 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.

Model	Per session	Once invoked
Fable 5.1	$0.00062	$0.01620
Opus 5.5	$0.00025	$0.00648
Sonnet 5.5	$0.00012	$0.00324
Haiku 4.5	$0.00006	$0.00162

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

Security

Grade A, and why

new-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 28d 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.

.claude/skills/new-issue/SKILL.md · 104 lines

How it starts

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

Turn a free-text description into a well-formed GitHub issue and post it.

⚠️ Guardrail: bayes-platform is PUBLIC

bayesimpact/bayes-platform is a public repository. Anything posted there (titles, bodies, comments, labels) is world-readable.

NEVER mention the "Health" project — or anything that identifies it — in any issue, body, or comment on bayes-platform. Strip it from the user's description and rephrase in neutral, generic terms.
More broadly, never include client names, confidential project names, internal URLs, credentials, or private data in anything posted to a public repo.
Never mention bayesimpact/internal-issues (or any other private repo) in bayes-platform — not in issue text, PR bodies, commit messages, Closes/Refs/Fixes trailers, or docs. Private-tracker IDs stay in private trackers and in chat with the user only.
If the user's description leans on a confidential detail to make sense, genericize it (e.g. "a specific client deployment") rather than dropping the issue. If you cannot genericize it without losing the point, STOP and ask the user how to phrase it.

This guardrail overrides "Friction is the enemy" — when confidentiality is at stake, pause and check rather than post.

Target repository

Default repo: bayesimpact/bayes-platform.

Override only if the user explicitly names another repo in the invocation (e.g. /new-issue --repo owner/name ... or "sur le repo X"). Otherwise always use the default — do NOT infer the repo from the current working directory.

Security issues always go to the private bayesimpact/internal-issues repo, never to bayes-platform, even when the user did not name a repo. This covers access-control gaps, permission bypasses, vulnerabilities, data exposure, and anything describing how to reach data a caller should not see. Use --repo bayesimpact/internal-issues for both the duplicate search and the creation. If you are unsure whether an issue is security-related, treat it as one.

Read the full file on GitHub · 104 lines

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.

28d ago Changed · +1 lines ff292bb8380a
1mo ago Changed · +2 lines 939c6c566df0
1mo ago First seen · 101 lines · 62 tokens per session scan A d66015c1cbd8

Subscribe to this mod's changes

new-issue is a skill published in the GitHub repository bayesimpact/bayes-platform (23 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,620 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-14.

Project management

new-issue next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
new-issuebayesimpact/bayes-platform	Skill	23	yesterday	MIT	A	62	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

bayes-platform: Skill for Claude Code