Borrowing it
Nothing to install: this file belongs to martin-francois/symphony-trello. 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/martin-francois/symphony-trello/main/.agents/skills/publish-bugbash-issues/SKILL.mdgit clone --depth 1 https://github.com/martin-francois/symphony-trelloWrote 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/martin-francois/symphony-trello/publish-bugbash-issues)<a href="https://agentmods.dev/skills/martin-francois/symphony-trello/publish-bugbash-issues"><img src="https://agentmods.dev/badge/skills/martin-francois/symphony-trello/publish-bugbash-issues/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/martin-francois/symphony-trello/publish-bugbash-issues"><img src="https://agentmods.dev/badge/skills/martin-francois/symphony-trello/publish-bugbash-issues.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.00044 | $0.01495 |
| Opus 5 | $0.00022 | $0.00747 |
| Sonnet 5 | $0.00009 | $0.00299 |
| Haiku 4.5 | $0.00004 | $0.00150 |
Grade A, and why
publish-bugbash-issues 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 10d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish bug-bash issues
Use this skill only after a person has reviewed local issue drafts created by $live-bugbash and
explicitly asks to post them to GitHub. The reviewer must also complete each selected draft's
AI Assistance (if used) human-review confirmation field before publication.
Do not use this skill for bug discovery. Do not run Symphony. Do not create Trello boards. Do not run Codex app-server. Do not create GitHub sandbox repositories. This skill only reads local issue drafts and posts reviewed results to the target GitHub repository.
Implicit invocation is disabled in agents/openai.yaml; do not select this skill accidentally.
Normal command
/goal Use $publish-bugbash-issues for RUN_ID=live-bugbash-20260629T103000Z. I reviewed the drafts and approve posting them to martin-francois/symphony-trello.
Defaults
Unless explicitly overridden:
TARGET_REPO=martin-francois/symphony-trello
RUN_ROOT=target/live-bugbash/<RUN_ID>
DRAFT_DIR=target/live-bugbash/<RUN_ID>/issues
DUPLICATE_ACTION=comment-with-reproduction-details
LABEL_POLICY=use-existing-labels-only
PUBLISH_SELECTION=confirmed-only
Before reading drafts or writing publication metadata, validate RUN_ID as one safe path segment:
ASCII letters, digits, ., _, and - only; not empty; not . or ..; no slash, backslash,
control character, shell metacharacter, or percent-encoded separator. Resolve and normalize
RUN_ROOT and DRAFT_DIR; DRAFT_DIR must stay under RUN_ROOT, and default run roots must stay
under target/live-bugbash/. Stop if an override points outside the reviewed run-owned location.
Publication guard
Posting to TARGET_REPO is forbidden unless the goal affirmatively contains both:
- A clear posting instruction, such as
post these drafts,publish these reviewed drafts, orcreate GitHub issues from these drafts. - A human-review approval phrase, such as
I reviewed the draftsorI have reviewed the drafts.
The skill name, default prompt text, or a denied phrase such as do not publish, do not comment,
preview only, or dry run does not count as posting approval. If either signal is missing or
negated, do not publish, do not comment, and explain the exact command the operator can use after
reviewing the drafts. Never infer approval from the existence of issue drafts.
What ships with it
2 files 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.
- 10d ago First seen · 140 lines · 44 tokens per session scan A c38eee95624a
publish-bugbash-issues is a skill published in the GitHub repository martin-francois/symphony-trello (2 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 1,495 once invoked, about $0.0002 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-31.
Other skills, from other repositories
shipit
Lands a reviewed pull request. Trigger on "ship it", "land the PR", "land this", or "/shipit" only; never infer ship intent from approval, green CI, or completion.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
langsmith-tracing
LangSmith tracing and debugging setup for LLM applications. Configure observability, capture traces, and enable debugging for LangChain/LangGraph agents.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.