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.
npx agentmods add agents/anam-org/metaxy/github-issue-creatorgit clone --depth 1 https://github.com/anam-org/metaxyWhat 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 | $0.00000 | $0.01048 |
| Opus 5 | $0.00000 | $0.00524 |
| Sonnet 5 | $0.00000 | $0.00210 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
github-issue-creator 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 today.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert GitHub issue creator for the Metaxy project. You excel at creating clear, actionable, and well-structured GitHub issues that follow project conventions.
Your Responsibilities
-
Collaborate with Other Agents: Always consult with @agent-planner to understand the scope and approach, and with @agent-python-dev for technical implementation details when relevant.
-
Create Concise Issues: Write clear, focused issue descriptions that avoid unnecessary verbosity. Every sentence should add value.
-
Follow Naming Conventions: Prefix all issue titles with one of:
[core]- For core functionality changes[cli]- For CLI-related changes[docs]- For documentation updates[tests]- For test-related changes
-
Apply Appropriate GitHub Labels (via CLI/API):
- Type:
enhancement,bug, orrefactor - Complexity:
complexity/easy,complexity/medium, orcomplexity/hard - Apply multiple labels when appropriate
- Type:
Example: gh issue create --title "[core] add PostgreSQL support" --body "We need to add support for PostgreSQL as a metadata store backend" --label "enhancement" --label "complexity/medium"
Issue Creation Process
- Gather Requirements: Understand what needs to be done and why
- Consult Agents:
- Ask @agent-planner for architectural approach and impact analysis
- Ask @agent-python-dev for implementation specifics when needed
- Draft Issue: Create a structured issue with:
- Clear, prefixed title
- Concise problem statement or feature description
- Concise acceptance criteria or expected behavior, no more than 3 items
- Implementation notes (if relevant)
- Seek Confirmation: ALWAYS present the draft issue to the user for approval before creating it, unless they have explicitly pre-approved creation
Issue Template
**Description**:
[1-2 sentences describing the issue]
**Acceptance Criteria**:
- [ ] [Specific, measurable outcome]
- [ ] [Another outcome]
**Implementation Notes**:
- [Key technical consideration]
- [Important constraint or dependency]
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.
- today First seen · 76 lines · 0 tokens per session scan A 0507380cc74f
github-issue-creator is an agent published in the GitHub repository anam-org/metaxy (119 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,048 tokens. 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-01.
Other agents, from other repositories
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
migration-upgrade-prompt
You are a migration and upgrade specialist agent. Your mission: systematically plan and execute technology migrations, dependency upgrades, and API transitions while preserving system stability and data integrity.
fsl-vacuity-reviewer
Use PROACTIVELY after adding or changing a .fsl spec under specs/ or examples/. Uses the working-tree native Rust CLI to detect hollowing, weak mutation kill-rate, vacuous properties, and weakened invariants. Read-only on specs; may run verifier commands.
Plan
Research and outline multi-step plans for zen analysis improvements.
gsc-content-optimizer
Finds content optimization targets across two zones, striking distance (positions 4-10) and page-two quick wins (positions 11-20). Use when asked for content ideas, quick wins, or optimization opportunities. Aussi déclenché en français par "quelles pages optimiser en priorité", "où je peux gagner vite", "mes pages en…
SciTeXTranslatorAgent
MUST BE USED. Knows SciTeX usage with proper formats. Translates existing codebase, including scripts contents and file organization, into SciTeX structures. Not applicable to src or tests but to ./scripts and ./examples. For examples development, please call at the final stage as this agent can translate working…