docs-code-sync

Project rules for keeping documentation and code aligned in an open-source application that extracts password hashes from multiple formats and platforms.

In plain words
What is it for?
Use them when changing extraction flows, hash formats, shared result structures, exporters, privacy behavior, or the related architecture documentation.
Why use it?
They reduce inconsistencies between the product, its documentation, its user interface, and its privacy rules when behavior changes.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/dosoos/catpasswd-hash-extract/docs-code-sync
Clone the repo
git clone --depth 1 https://github.com/dosoos/Catpasswd-Hash-Extract

Made for: Cursor.

Per session 139 This file is loaded in full into every session.
When invoked 139 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00139 $0.00139
Opus 5 $0.00069 $0.00069
Sonnet 5 $0.00028 $0.00028
Haiku 4.5 $0.00014 $0.00014

Measured yesterday against content hash ba902991433f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docs-code-sync 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 yesterday.

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.

.cursor/rules/docs-code-sync.mdc · 14 lines

What it actually says

Catpasswd Hash Extract

  • Read AGENTS.md and docs/architecture.md before changing product behavior.
  • Goal: unified multi-format, multi-platform hash extraction with a stable HashResult for John/hashcat/exporters.
  • Keep docs and UI neutral and open-source focused.
  • Align docs with logic and constraints, not folder trees. Keep docs short.
  • Extraction in Rust via Tauri IPC; first-party native extractors only in production.
  • Update docs/architecture.md when changing flows, HashResult, formats, or privacy rules.
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.

  1. yesterday First seen · 14 lines · 139 tokens per session scan A ba902991433f

Subscribe to this mod's changes

docs-code-sync is a cursor rule published in the GitHub repository dosoos/Catpasswd-Hash-Extract (5 stars, last pushed 29d ago), licensed MIT. It adds 139 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-31.