Borrowing it
Nothing to install: this file belongs to ky2renzzz/acp-forge. 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/ky2renzzz/acp-forge/master/.grok/skills/forge-session/SKILL.mdgit clone --depth 1 https://github.com/ky2renzzz/acp-forgeWrote 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/ky2renzzz/acp-forge/forge-session)<a href="https://agentmods.dev/skills/ky2renzzz/acp-forge/forge-session"><img src="https://agentmods.dev/badge/skills/ky2renzzz/acp-forge/forge-session/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/ky2renzzz/acp-forge/forge-session"><img src="https://agentmods.dev/badge/skills/ky2renzzz/acp-forge/forge-session.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.00031 | $0.00230 |
| Opus 5.5 | $0.00012 | $0.00092 |
| Sonnet 5.5 | $0.00006 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
forge-session 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 2mo 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
Forge Session
Manage reproducible execution sessions.
Commands
List sessions
cargo run --manifest-path <path-to-acp-forge>/Cargo.toml -- session list
Verify session integrity
cargo run --manifest-path <path-to-acp-forge>/Cargo.toml -- session verify <path-to-session.json>
Checks every event's SHA-256 content hash and the session's integrity hash.
Diff two sessions
cargo run --manifest-path <path-to-acp-forge>/Cargo.toml -- session diff <session-a.json> <session-b.json>
Finds the first point where two sessions diverge.
Use Cases
- Audit: verify that a recorded session was not tampered with
- Debug: replay a failing session to find the exact divergence point
- Compare: diff two runs of the same task to see what changed
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.
- 2mo ago First seen · 33 lines · 31 tokens per session scan A c57a580bcbed
forge-session is a skill published in the GitHub repository ky2renzzz/acp-forge (5 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 230 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
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
rpa-bugfix
Run when the user invokes /rpa-bugfix together with a clear bug description (expected vs actual, reproduction). Reproduction test first, then fix, full test suite, short report. Will not work correctly without the bug details.
debug-test-failure
Systematically diagnose a failing test instead of guessing at fixes.
eval-integration
Specialized integration evaluator for the Evaluate-Loop. Use this for evaluating tracks that integrate external services — Supabase auth/DB, Stripe payments, Gemini API, third-party APIs. Checks API contracts, auth flows, data persistence, error recovery, environment config, and end-to-end flow integrity. Dispatched…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
eval-business-logic
Specialized business logic evaluator for the Evaluate-Loop. Use this for evaluating tracks that implement core product logic — pipelines, dependency resolution, state machines, pricing/tier enforcement, packaging. Checks feature correctness against product rules, edge cases, state transitions, data flow, and user…