Borrowing it
Nothing to install: this file belongs to JNZader/repoforge. 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/JNZader/repoforge/main/.claude/skills/build_modules/incremental/SKILL.mdgit clone --depth 1 https://github.com/JNZader/repoforgeWrote 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/jnzader/repoforge/incremental)<a href="https://agentmods.dev/skills/jnzader/repoforge/incremental"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/incremental/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/jnzader/repoforge/incremental"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/incremental.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.00026 | $0.00505 |
| Opus 5.5 | $0.00010 | $0.00202 |
| Sonnet 5.5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
add-incremental-endpoint 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 24d 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
add-incremental-endpoint
One sentence: Handles incremental chapter dependency tracking and manifest persistence for the repoforge build system.
Trigger: incremental or manifest operations
Quick Reference
| Task | Pattern |
|---|---|
| Load manifest | load_manifest(out_dir) |
| Get git SHA | get_git_sha(repo_root) |
| Check stale chapters | stale_chapter_names(changed_files, consumed_by_chapter) |
Critical Patterns (Detailed)
Pattern 1: Manifest Persistence
Load and save the manifest to track chapter state across incremental builds.
# Load existing manifest
manifest: Optional[Manifest] = load_manifest(out_dir)
# Save updated manifest after changes
save_manifest(out_dir, manifest) # type: ignore
Pattern 2: Stale Chapter Detection
Identify which chapters need rebuilding after file changes by comparing dependencies.
# Detect chapters that are stale due to changed files
stale: list[str] = stale_chapter_names(changed_files, consumed_by_chapter)
When to Use
- After git operations to determine which chapters need rebuilding
- When file changes invalidate chapter dependencies
- Before running incremental builds to skip up-to-date chapters
Commands
# Run incremental build
python -m repoforge.cli build --incremental
# Check git state
python -c "from repoforge.incremental import get_git_sha; print(get_git_sha(Path('.')))"
Anti-Patterns
Don't: Skip dependency tracking
# BAD: Assuming no chapters are stale without checking dependencies
stale = [] # Wrong: never empty if files changed
# BAD: Missing manifest persistence
save_manifest(out_dir, manifest) # Required after chapter changes
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.
- 24d ago Changed · -23 lines · +1 tokens per session 354ba3fa356b
- 25d ago First seen · 111 lines · 25 tokens per session scan A 48d724fbfdaf
add-incremental-endpoint is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 24d ago), licensed MIT. It adds 26 tokens to every session and 505 once invoked, about $0.0001 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-09-27.
Other skills, from other repositories
github
GitHub CLI (gh) for repository management, issues, pull requests, releases, workflows, search, gists, and API access. Use when the user asks about any GitHub operation — creating repos, forking, cloning, PR workflows, issue triage, CI/CD runs, code search, release management, or direct API calls. Keywords: github, gh…
pi-review-gated-delivery
Use when coordinating review-gated delivery of discrete GitHub issues between one implementation peer and a review-only lead, with user-owned Changesets and approval-gated commits.
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
github-issues
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.
github-issues
Create, triage, label, assign GitHub issues via gh or REST.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.