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/jaycewalzer1/SilverKey-Inc.Wrote 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/jaycewalzer1/silverkey-inc./package-feature-structure)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./package-feature-structure"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./package-feature-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/jaycewalzer1/silverkey-inc./package-feature-structure"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./package-feature-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.00000 | $0.00519 |
| Opus 5.5 | $0.00000 | $0.00208 |
| Sonnet 5.5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
package-feature-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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Package Feature Module Structure
Goal
Each package module (e.g. a feature under Client/packages/features/<name>/) must follow a single, enforced layout. Only the following direct children are allowed.
Allowed Structure
Under packages/features/<featureName>/ (and any other package scope that adopts this convention), the only allowed direct children are:
| Item | Purpose |
|---|---|
api/ |
Network requests and endpoint definitions |
components/ |
UI elements specific to this feature |
hooks/ |
Custom React hooks |
store/ |
Local state management |
types/ |
TypeScript interfaces and models |
utils/ |
Pure helper functions |
index.ts (or index.tsx / index.js) |
The public API (barrel file) |
No other files or folders may exist at the module root. Place new code in the appropriate allowed folder.
Example
packages/features/saved/
├── api/ # Network requests and endpoint definitions
├── components/ # UI elements specific to this feature
├── hooks/ # Custom React hooks
├── store/ # Local state management
├── types/ # TypeScript interfaces and models
├── utils/ # Pure helper functions
└── index.ts # The public API (barrel file)
Enforcement
- ESLint: Rule
silverkey/package-module-allowed-childrenruns onpackages/features/**and reports any file or folder that is not one of the allowed children. - Scope: By default the rule applies to
packages/features/. Optionally configurable for other package roots via rule options (scopeDir,allowedDirs,allowedRootFiles).
References
- Feature package README:
Client/packages/features/README.md - Cross-feature composition:
documentation/architecture/cross-feature-composition.md(barrels, orchestrators, import tiers) - Lint reference:
documentation/reference/linting.md(run lint; package-module-allowed-children is in ESLint) - Shared packages:
documentation/architecture/shared-packages.md
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 · 54 lines · 0 tokens per session scan A 0483d9a6ba60
package-feature-structure is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 519 tokens. 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-09-08.
Other cursor rules, from other repositories
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
selectools-providers
Rules for working with LLM provider adapters in selectools.