Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/logosdx/monoreponpx agentmods add rules/logosdx/monorepo/intent-and-structureWrote 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/logosdx/monorepo/intent-and-structure)<a href="https://agentmods.dev/rules/logosdx/monorepo/intent-and-structure"><img src="https://agentmods.dev/badge/rules/logosdx/monorepo/intent-and-structure/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/logosdx/monorepo/intent-and-structure"><img src="https://agentmods.dev/badge/rules/logosdx/monorepo/intent-and-structure.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.00013 | $0.00622 |
| Opus 5.5 | $0.00005 | $0.00249 |
| Sonnet 5.5 | $0.00003 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
intent-and-structure 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.
What it actually says
Intent & Structure
PNPM monorepo structure and organizational patterns for the @logosdx ecosystem.
Repository Structure
- Source code:
packages/*/src/- Each package has its own source directory - Documentation:
docs/- Centralized documentation for all packages - Tests:
tests/src/- Mirrors source structure for validation - Scripts:
scripts/- Build, release, and utility scripts - Configuration: Root-level configs for TypeScript, build tools, etc.
Package Organization
- Independent packages: Each package builds and publishes separately
- Shared dependencies: Internal packages depend on each other via published interfaces
- Cross-package imports: Use package names (
@logosdx/utils) not relative paths - Test imports: Use relative paths (
../../packages/utils/src/index.ts) to validate actual implementation
Error Handling Philosophy
- Fail-prone operations (I/O, network, async) → Use Go-style error tuple
[result, error] - Business logic functions → Return actual results directly
- Composition → Combine error tuple for I/O with direct returns for business logic
Build & Release
- Individual builds: Each package builds independently with its own config
- Coordinated releases: Use changeset for version management and releases
- Type generation: Shared TypeScript configs for consistent type generation
- Documentation: TypeDoc generation for each package
Development Workflow
- Package creation: Use
pnpm run newscript for new packages - Testing:
pnpm run testruns all tests,pnpm run tddfor development - Building:
pnpm run buildbuilds all packages - Documentation:
pnpm run build:docsgenerates TypeDoc
Quick Examples
# Create new package
pnpm run new
# Run tests
pnpm run test
pnpm run tdd
# Build everything
pnpm run build
# Generate docs
pnpm run build:docs
// ✅ Cross-package imports (production code)
import { attempt } from '@logosdx/utils';
import { ObserverEngine } from '@logosdx/observer';
// ✅ Test imports (relative paths)
import { attempt } from '../../../../packages/utils/src/index.ts';
import { ObserverEngine } from '../../../../packages/observer/src/engine.ts';
// ❌ Wrong import pattern in tests
import { attempt } from '@logosdx/utils'; // Won't validate actual implementation
// ✅ Error handling patterns
// Fail-prone operation (I/O)
const [user, err] = await attempt(() => fetchUser(userId));
if (err) throw err;
// Business logic (direct return)
const modifiedUser = modifyUserEmail(user, newEmail);
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 · 74 lines · 13 tokens per session scan A 336d190ac0b3
intent-and-structure is a cursor rule published in the GitHub repository logosdx/monorepo (7 stars, last pushed 10d ago), licensed BSD-3-Clause. It adds 13 tokens to every session and 622 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 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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).