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.
git clone --depth 1 https://github.com/hoangsonww/Forge-Agentic-Coding-CLIWrote 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/rules/hoangsonww/forge-agentic-coding-cli/forge-core)<a href="https://agentmods.dev/rules/hoangsonww/forge-agentic-coding-cli/forge-core"><img src="https://agentmods.dev/badge/rules/hoangsonww/forge-agentic-coding-cli/forge-core/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/rules/hoangsonww/forge-agentic-coding-cli/forge-core"><img src="https://agentmods.dev/badge/rules/hoangsonww/forge-agentic-coding-cli/forge-core.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.00601 | $0.00601 |
| Opus 5.5 | $0.00240 | $0.00240 |
| Sonnet 5.5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
forge-core 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge — core conventions
Forge is a local-first, multi-agent, programmable software-engineering
CLI runtime (TypeScript, Node 20+). Ships as @hoangsonw/forge on npm
and as a multi-arch Docker image.
Canonical verify chain
Before claiming any change done:
npm run format && npm run lint && npm run build && npm test
249 tests across 43 files must remain 100% passing.
Hot paths — surgical edits only
src/core/loop.ts— agentic pipelinesrc/agents/executor.ts— iterative tool-use loopsrc/core/mode-policy.ts— per-mode capssrc/core/validation.ts— post-step gatesrc/models/router.ts+src/models/adapter.ts— routingsrc/persistence/tasks.ts— state machine +LEGAL_TRANSITIONS
Non-negotiables
- Every tool call goes through
requestPermission(src/permissions/manager.ts). - Paths resolved to realpath and confined to project root
(
src/sandbox/fs.ts). - Shell commands classified by
classifyCommandRisk(src/sandbox/shell.ts);criticalis hard-blocked. - Credentials in OS keychain (
src/keychain/), never in config files. - State transitions live in
LEGAL_TRANSITIONS— never monkey-patch.
Style
- TypeScript strict. No
anyin production without a comment explaining why (exception:src/tools/registry.ts). - Comments explain why, not what. Never add a comment that describes the change you just made.
- Prefer
readonlyand immutable data flow. Prefer function modules over classes (exception: provider classes insrc/models/). - Throw
ForgeRuntimeError(src/types/errors.ts) with{ class, message, retryable, recoveryHint? }. UseResult<T, E>shapes for expected failures.
Performance posture
- REPL cold-start < 250 ms.
forge doctor< 1 s with no providers running.- UI
app.js< 120 KB uncompressed. - No synchronous disk reads on REPL redraw or UI poll paths.
- Provider availability probes ~1.5 s, not long timeouts.
Before adding a dependency, ask whether a 20-line hand-written utility would do. It usually would.
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 · 70 lines · 601 tokens per session scan A c0eea1133b0c
forge-core is a cursor rule published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (26 stars, last pushed 18d ago), licensed MIT. It adds 601 tokens to every session, about $0.0024 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.