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 github-pr-descriptiongit 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/github-pr-description)<a href="https://agentmods.dev/skills/tailcallhq/forgecode/github-pr-description"><img src="https://agentmods.dev/badge/skills/tailcallhq/forgecode/github-pr-description/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/github-pr-description"><img src="https://agentmods.dev/badge/skills/tailcallhq/forgecode/github-pr-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 143 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00072 | $0.02411 |
| Opus 5.5 | $0.00029 | $0.00964 |
| Sonnet 5.5 | $0.00014 | $0.00482 |
| Haiku 4.5 | $0.00007 | $0.00241 |
Grade A, and why
github-pr-description scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:3000/search \ Copies of this mod
1 near-identical copy found in the catalogue:
- github-pr-description — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR Description
Generate comprehensive pull request descriptions and create PRs using GitHub CLI.
Workflow
1. Verify Prerequisites
Check that there are changes to create a PR for:
# Get current branch
git branch --show-current
# Verify branch is not main/master
# Verify there are commits ahead of main
git log origin/main..HEAD --oneline
If on main/master or no commits ahead, inform the user there's nothing to create a PR for.
2. Analyze Changes
Gather context about the changes:
# Get commit messages
git log origin/main..HEAD --pretty=format:"%s"
# Get diff summary (files changed)
git diff origin/main..HEAD --stat
# Get actual code changes (sample key files if diff is large)
git diff origin/main..HEAD
For large diffs: Focus on the most meaningful changes. Sample key files rather than reading everything.
3. Determine Change Type
Classify the PR into one of these categories:
- fix: Bug fixes, error corrections, resolving issues
- feature: New functionality, capabilities, or enhancements
- performance: Speed improvements, optimization, efficiency gains
- refactor: Code restructuring without changing behavior
- docs: Documentation changes
- test: Test additions or improvements
- chore: Maintenance tasks, dependencies, configuration
Base this on:
- Commit messages (keywords like "fix", "add", "optimize", "refactor")
- Nature of code changes (new files = feature, test fixes = fix, etc.)
- Scope of changes
4. Generate Description
Create a comprehensive description with this structure:
## Summary
[One sentence explaining what this PR does and why it matters]
## Context
[Background information, related issues, previous work, or the problem being solved]
## Changes
[High-level description of what changed]
### Key Implementation Details
[Technical details that help reviewers understand the approach, especially for complex changes]
## Use Cases
[Concrete examples of how this will be used - helps reviewers understand practical value]
## Testing
[How to test the changes - step-by-step instructions]
## Links
- Related issues: #123, #456
- Documentation: URL (if applicable)
- Original implementation: URL (if applicable)
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 · 351 lines · 72 tokens per session scan A 0eb8bfd663f0
github-pr-description is a skill published in the GitHub repository tailcallhq/forgecode (7,636 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 2,411 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
app-store-changelog
Generate user-facing App Store release notes from git history since the last tag.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, canonical sync, Core preview checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
release
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
commit-msg
You receive a git diff of staged changes via stdin. Generate a commit message.