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./thin-app-architecture)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./thin-app-architecture"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./thin-app-architecture/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./thin-app-architecture"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./thin-app-architecture.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.00468 | $0.00468 |
| Opus 5.5 | $0.00187 | $0.00187 |
| Sonnet 5.5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
thin-app-architecture 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
Thin App (Fat Packages) Architecture
Client/apps/web and Client/apps/mobile are composition and routing shells. Product logic belongs in Client/packages/**.
What Belongs in the Thin App Folders
Allowed in apps/web and apps/mobile
- Configuration and entry points
- App-level env wiring
- Routing map
- Web:
<BrowserRouter>and route list (e.g./login,/dashboard) - Mobile:
<Stack.Navigator>, bottom tabs, screen registration - Workspace shells stay thin; workspace state/logic lives in
packages/.
- Web:
- Page/screen composition using shared components/hooks
- Platform wrappers (
SafeAreaProvider, global layout wrappers)
Forbidden in apps (belongs in packages)
- Business logic, data-fetching orchestration, or non-trivial state logic (→
packages/hooks/,packages/services/,packages/utils/) - Reusable UI primitives or feature components (→
packages/or shared UI) - Standalone
.tsutilities or formatters underapps/web/components/orapps/web/features/(→packages/utils/,packages/schemas/)
Page/Screen Pattern
App pages/screens should compose shared pieces, not implement them:
// ✅ CORRECT: Thin composition in apps/web/pages/Dashboard.tsx
import { DashboardLayout, DashboardWidget } from '@silverkey/ui'; // or packages path
import { useUserData } from '@silverkey/hooks';
export function WebDashboard() {
const { user } = useUserData();
return (
<DashboardLayout>
<DashboardWidget data={user} />
</DashboardLayout>
);
}
- No inline data-fetching, no complex conditionals, no new primitives. If you need a new widget or hook, add it in
packages/and import it here.
Reference
- Full rationale/examples:
documentation/architecture/thin-app-architecture.md. - Layering/import constraints:
frontend-architecture.mdc.
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 · 53 lines · 468 tokens per session scan A 005fe5030cb9
thin-app-architecture is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It adds 468 tokens to every session, about $0.0019 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-09-08.
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-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).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.