Forge is a command-line development environment that uses AI models as a pair programmer for working with code and shell commands. Developers use it to understand projects and carry out coding tasks through interactive, one-shot, or ZSH-based workflows. The catalogue entries extend Forge with reusable skills, agents, commands, and instructions.
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 skills add tailcallhq/forgecode --skill create-github-issuegit clone --depth 1 https://github.com/tailcallhq/forgecodeWrote 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/tailcallhq/forgecode/create-github-issue)<a href="https://agentmods.dev/skills/tailcallhq/forgecode/create-github-issue"><img src="https://agentmods.dev/badge/skills/tailcallhq/forgecode/create-github-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.
<a href="https://agentmods.dev/skills/tailcallhq/forgecode/create-github-issue"><img src="https://agentmods.dev/badge/skills/tailcallhq/forgecode/create-github-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.00989 |
| Opus 5.5 | $0.00025 | $0.00396 |
| Sonnet 5.5 | $0.00013 | $0.00198 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
create-github-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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create-github-issue — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Issue
Create comprehensive GitHub issues using gh issue create by dynamically discovering and adhering to the repository's official issue templates.
Workflow
1. Discover and Select Template
CRITICAL: You must use the repository's official templates. Do not assume the structure.
- List available templates:
ls .github/ISSUE_TEMPLATE/ - Select the most appropriate template based on the issue type (e.g.,
bug_report.yml,feature_request.yml). - Read the selected template to understand its required fields, structure, and any title prefixes or default labels.
cat .github/ISSUE_TEMPLATE/<selected_template>.yml
2. Gather Context
Gather relevant information to fulfill the template requirements:
# Check current git status for context
git status
# View recent commits if related to codebase changes
git log --oneline -10
# Check if related issues exist
gh issue list --search "keyword" --limit 10
3. Generate Markdown Body
MANDATORY: Structure the issue body exactly as defined in the selected YAML template without exception.
- Map YAML fields to Markdown: Convert each field in the template (typically found under
body:) into a Markdown section. - Use Headers: Use the
labeloridfrom the YAML field as an H2 header (e.g.,## Bug Description). - Respect Validation: Ensure all fields marked as
required: truein the YAML are populated with meaningful content. - Format Correctly: Use code blocks (e.g.,
```shell,```yaml) for logs and configurations as suggested by the template'srenderattribute.
4. Choose Labels
Select labels by inspecting .github/labels.json.
- Primary Label: Always include a
type:label that matches the issue type. - Additional Labels: Add relevant
state:,work:, orpriority:labels if they exist in the configuration. - Constraint: Only use labels defined in
.github/labels.json.
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.
- 1mo ago First seen · 99 lines · 63 tokens per session scan A ca343317ef87
create-github-issue is a skill published in the GitHub repository tailcallhq/forgecode (7,638 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 989 once invoked, about $0.0003 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-30.
Other skills, from other repositories
mbo-plan
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…
finalize-phase
Completes feature/epic workflows after deployment with comprehensive walkthrough generation for epics (v5.0+), roadmap updates, artifact archival, documentation, and branch cleanup. Use after /ship-prod, /deploy-prod, or /build-local completes, or when user asks to finalize. (project).
workflow-detection
Provides centralized workflow type detection for all phase and deployment commands.
github-brief-intake
Use when GitHub work should enter the repository work-intake route, including an Issue, Milestone, view, or cross-repository selection.
caro-leftovers
Document leftover tasks as GitHub issues with full correlation to branch, PR, and original work plan. Use when ending a session with incomplete work that another agent should pick up.
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.