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.
git clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/commands/athola/claude-night-market/promote-discussions)<a href="https://agentmods.dev/commands/athola/claude-night-market/promote-discussions"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/promote-discussions/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/commands/athola/claude-night-market/promote-discussions"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/promote-discussions.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.00020 | $0.00495 |
| Opus 5 | $0.00010 | $0.00247 |
| Sonnet 5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
promote-discussions 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 12d 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.
What it actually says
Promote Community Learnings
Check GitHub Discussions for highly-voted learnings and promote them to Issues.
Usage
/abstract:promote-discussions
Purpose
Part of Issue #69 Phase 6c, this command scans athola/claude-night-market Discussions in the "Learnings" category for items that have received sufficient community votes (fire emoji reactions) and promotes them to GitHub Issues for team triage.
What It Does
- Loads config from
~/.claude/skills/discussions/config.jsonpromotion_threshold: Minimum fire reactions to promote (default: 3)promotion_emoji: Reaction type to count (default: fire)
- Queries Discussions in the "Learnings" category via
gh api graphql - Checks reaction counts for fire emoji specifically
- Promotes qualifying items by creating GitHub Issues with:
- Title:
[Community Learning] {discussion title} - Body: Link to discussion, vote count, original content summary
- Title:
- Tracks promotions in
~/.claude/skills/discussions/promoted.jsonto avoid duplicates
Instructions
When this command is invoked:
- Run
plugins/abstract/scripts/promote_discussion_to_issue.py - Report results to the user:
- If items were promoted: list the created Issue URLs
- If no items met the threshold: report the current threshold and suggest waiting for more votes
- If an error occurred: report the error and suggest checking
gh auth status
Prerequisites
- GitHub CLI (
gh) must be installed and authenticated - User must have write access to athola/claude-night-market (for Issue creation)
Configuration
Edit ~/.claude/skills/discussions/config.json:
{
"promotion_threshold": 3,
"promotion_emoji": "🔥"
}
Related
/abstract:aggregate-logs- Generates LEARNINGS.md and posts to Discussions (Phase 6a)/abstract:improve-skills- Implements improvements locally (Phase 5)
Version
1.0.0 (Phase 6c implementation)
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.
- 12d ago First seen · 66 lines · 20 tokens per session scan A 09536c6b70ec
promote-discussions is a command published in the GitHub repository athola/claude-night-market (337 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 495 once invoked, about $0.0001 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.
Other commands, from other repositories
github-issue-fix
This is a detailed way you can analyze the GitHub issues and let Claude handle them in best possible way.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
weekly-summary
Generate weekly work summary from git activity.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
parallel
You are executing the /hydra:parallel command. Start multiple agents simultaneously in different worktrees.
cd-branch
Create a Conductor branch CARD and brief (does not open a session). Master only.