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 agentmods add rules/os-factory/har/har-workflowgit clone --depth 1 https://github.com/os-factory/harWhat 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 | $0.00132 | $0.00132 |
| Opus 5 | $0.00066 | $0.00066 |
| Sonnet 5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
har-workflow 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 2d 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
HAR Harness Workflow
This repository uses a .har/ agent harness. Read AGENTS.md
and follow it — it is the single source of truth for the harness workflow
(launch a slot first, edit only in the work dir, full verify before done, stop at
handoff). .har/README.md has the harness detail.
This rule exists only to guarantee that instruction reaches every Cursor session; it deliberately does not restate the workflow, so there is one copy to keep current.
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.
- 2d ago First seen · 15 lines · 132 tokens per session scan A 3e1ea81a095c
har-workflow is a cursor rule published in the GitHub repository os-factory/har (83 stars, last pushed 2d ago), licensed Apache-2.0. It adds 132 tokens to every session, about $0.0007 per session on Opus 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
trueforge-ui-slots
Every newly created or newly JSX-bearing component in @truefoundry/trueforge-ui MUST be host-overridable through the slots system. Do not hard-import leaf UI into layouts/containers when a slot exists (or should exist).
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
scope-enforcement
Enforces strict scope boundaries on every file modification. Prevents unauthorized out-of-scope changes.
ux-audit
UX audit and design guidance skill.
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.