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 luiseiman/dotforge --skill diff-projectgit clone --depth 1 https://github.com/luiseiman/dotforgeWrote 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/luiseiman/dotforge/diff-project)<a href="https://agentmods.dev/skills/luiseiman/dotforge/diff-project"><img src="https://agentmods.dev/badge/skills/luiseiman/dotforge/diff-project/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/luiseiman/dotforge/diff-project"><img src="https://agentmods.dev/badge/skills/luiseiman/dotforge/diff-project.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.00025 | $0.00652 |
| Opus 5.5 | $0.00010 | $0.00261 |
| Sonnet 5.5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
diff-project 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diff Project
Show what changed in dotforge since the last synchronization of the current project.
Step 1: Identify project baseline
- Read
$DOTFORGE_DIR/registry/projects.local.yml - Find the current project by
path(compare with$PWD) - Get
dotforge_versionandlast_sync - If no
dotforge_versionis registered (null), report:
And stop.Project not synced — no baseline to compare against. Run /forge sync to establish baseline.
Step 2: Verify local manifest
If .claude/.forge-manifest.json exists in the current project:
- Read it and get the version and file hashes
- For each file in the manifest, calculate
shasum -a 256 <file> | cut -d' ' -f1 - Compare against the registered hash
- Report locally modified files (hash differs) and deleted files
- Use the manifest version as baseline (more precise than the registry)
If manifest does NOT exist, continue to Step 3 using git log.
Step 3: Detect changes in dotforge
Run in $DOTFORGE_DIR/:
git log --oneline v<version>..HEAD -- template/ stacks/
Where <version> is the tag corresponding to the project's dotforge_version.
If the tag does not exist, use last_sync as reference:
git log --oneline --since="<last_sync>" -- template/ stacks/
If there are no relevant commits, report:
dotforge has no changes in template/stacks since v<version>.
Project is up to date.
Step 4: Show change summary
For each modified file in template/ or relevant stacks/ for the project:
═══ DIFF dotforge: v<previous> → v<current> ═══
Project: <name> (last sync: <date>)
Files modified in dotforge:
template/hooks/block-destructive.sh — <diff summary>
template/rules/_common.md — <diff summary>
stacks/python-fastapi/rules/backend.md — <diff summary>
Local files with modifications (vs manifest):
.claude/rules/_common.md — hash differs from deployed
Filter stacks/ to show only the stacks used by the project (read from registry).
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.
- 9d ago Changed 5b6c52b4a75a
- 1mo ago First seen · 91 lines · 25 tokens per session scan A b177698e1fe7
diff-project is a skill published in the GitHub repository luiseiman/dotforge (8 stars, last pushed 9d ago), licensed MIT. It adds 25 tokens to every session and 652 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-08-31.
Other skills, from other repositories
release-notes
A release-automation tool that uses Conventional Commits, a standard commit-message format, to prepare a software release.
shipping-and-launch
A pre-launch checklist and rollout guide for releasing software safely. It covers quality checks, monitoring, staged releases, and plans for reversing a release if something goes wrong.
git-hygiene
Git repository hygiene check. Stale branches, large files, commit conventions. Use when: "git cleanup", "git hygiene", "clean up branches", "git-hygiene", "stale branches", "git cleanup".
worktree
Use when the user wants to work in an isolated branch, start a safe development environment, or avoid polluting the main branch.
commit
Use when the user wants to commit changes, save work, or create a git commit message.
changelog
Use when the user wants a changelog, release notes, or asks what changed since the last release.