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/0xranx/golembot/architecture-constraintsgit clone --depth 1 https://github.com/0xranx/golembotWhat 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.00000 | $0.00576 |
| Opus 5 | $0.00000 | $0.00288 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
architecture-constraints scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
5. **Process invocation is engine-owned** — All engines use `child_process.spawn`. Do not assume invocation style outside the engine. How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Hard Constraints
When modifying code under src/, the following constraints must not be violated. To relax them, first update docs/architecture.md.
Things You Must Never Do
- Don't do what the Agent should do — GolemBot does not manage context window, dispatch tools, reason, or set session TTL. All "intelligent" behavior is delegated to the underlying Coding Agent.
- Don't add new core concepts — The framework has only two concepts: assistant directory + Skill. Do not introduce Tool, Blueprint, Registry, Pipeline, or other abstractions.
- Don't put CLI logic in the core library —
cli.tsis a thin shell; it only parses arguments and formats output. All business logic must live inindex.ts/workspace.ts/engine.ts/session.ts/server.ts. - Don't declare Skills in config — The
skills/directory is the single source of truth.golem.yamlonly configures engine and name. - Process invocation is engine-owned — All engines use
child_process.spawn. Do not assume invocation style outside the engine.
Interface Change Rules
- Any signature change to the
Assistantinterface (index.ts) must be reflected in docs/architecture.md Chapter 5 (API definition) - Any change to the
AgentEngineinterface (engine.ts) must be reflected in docs/architecture.md Chapter 7 StreamEventtype changes must verify compatibility withserver.tsSSE output andcli.tsevent handling
File Responsibility Boundaries
| File | Responsibility | Should Not Contain |
|---|---|---|
index.ts |
Public API, concurrency locks, orchestration of workspace/engine/session | Engine implementation details, HTTP logic |
engine.ts |
Engine interface, Cursor / Claude Code implementations, stream-json parsing, Skill injection | Session management, config loading |
workspace.ts |
golem.yaml read/write, skills scanning, AGENTS.md generation | Engine invocation, session management |
session.ts |
Session persistence (indexed by sessionKey) | Any other logic |
server.ts |
HTTP service, SSE, auth | Engine implementation details |
cli.ts |
Argument parsing → call core API → format output | Business logic |
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.
- yesterday First seen · 41 lines · 0 tokens per session scan A b6084848f018
architecture-constraints is a cursor rule published in the GitHub repository 0xranx/golembot (318 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 576 tokens. A static security scan graded it A with 1 finding (runs shell commands). 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
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.
skill-conventions
Project conventions for creating and editing Obsidian vault skills.
qmd-search
Prefer QMD over grep/ripgrep for searching vault content.
commits
Guidance on commit messages.
migration
Cursor rule "migration" from sunmh207/entire-dashboard, covering migration 数据库迁移脚本规范, 1. 目录结构, 2. 脚本文件命名规范, 3. 数据库与字符集规范 and 4. 表、字段书写规范.