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/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/gstack)<a href="https://agentmods.dev/rules/bilal140202/the-lord-of-the-skills/gstack"><img src="https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/gstack/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/bilal140202/the-lord-of-the-skills/gstack"><img src="https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/gstack.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.00257 | $0.00257 |
| Opus 5 | $0.00129 | $0.00129 |
| Sonnet 5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
gstack 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 9d 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
GStack Engineering Rules
Workflow
- Scene A (Large Features): CEO Review → Eng Review → Pause for approval → Code → Module review → Global review
- Scene B (Bug Fix): Trace bug chain → Systematic root cause → Fix → Build verify
- Scene C (UI Tweak): Locate component → Precise edit → User confirms
- Scene D (Refactor): Review target → Small steps with build verification → No business logic changes
Quality Gates
- Zero silent failures: every catch block has user-visible feedback
- State completeness: every loading state has loaded/error counterpart
- Empty states: every list/table has empty state message
- Interaction feedback: every button has loading/disabled/animation response
- DRY: extract after 3+ repetitions
- No residuals: no console.log, no TODO, no hardcoded paths
- Type safety: no
anytype, complete interface definitions
Design Quality
- Style consistency: follow project design system
- Restrained animation: only enhance UX, no flashy effects
- Responsive: all grid layouts degrade gracefully
- Accessibility: hover and focus styles on all interactive elements
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.
- 9d ago First seen · 31 lines · 257 tokens per session scan A efb7cfb38726
gstack is a cursor rule published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 257 tokens to every session, about $0.0013 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-09-03.
Other cursor rules, from other repositories
agentic-clean-code
Language-agnostic agent-oriented clean code: file size limits, grep-friendly names, provenance comments, testability, and error context. Apply when writing or reviewing code in any stack.
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.
cli-error-handling
CLI command error handling patterns.
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.