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/genocs/genocs-library/solution_architectgit clone --depth 1 https://github.com/Genocs/genocs-libraryWhat 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.00790 |
| Opus 5 | $0.00000 | $0.00395 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
solution_architect 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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Core Library Best Practices and Coding Standards
This document outlines the recommended best practices for developing applications and infrastructure using Microsoft .NET Core, Azure DevOps and Azure services. It covers various aspects including solution setup, code organization, security, and tooling to ensure robust, scalable, and secure solutions.
1. Code Organization and Structure
A well-organized codebase is crucial for maintainability, scalability, and collaboration. The following guidelines provide a structured approach to organizing your .NET projects.
Directory Structure Best Practices
Adopt a modular and logical directory structure based on the application's architecture and components.
devops/: Contains the root folder for DevOps pipelines for your application.azure/: Contains the source code of Azure DevOps pipelines for your application.
infrastructure/: Contains the source code of IaC and platform setup scripts for your application.bicep/: Contains the source code of Bicep templates for your application.terraform/: Contains the source code of Terraform templates for your application.
scripts/: Automation scripts for deployment, build processes, etc.src/: Contains the source code of your application.
Example:
root-project/ ├── .cursor/ │ └── rules/ ├── .git/ ├── .github/ │ ├── chatmode │ ├── instructions │ └── workflows/ ├── devops/ │ └── azure/ ├── infrastructure/ │ ├── bicep/ │ └── terraform/ ├── scripts/ ├── src/ ├── .editorconfig ├── .gitattributes ├── .gitignore ├── CHANGELOG.md ├── CODE_OF_CONDUCT.md ├── Directory.Build.props ├── Directory.Build.targets ├── dotnet.ruleset ├── global.json ├── stylecop.json ├── nuget.config ├── project.sln └── README.md
File Naming Conventions
Maintain consistency in file naming to improve readability and searchability.
- Use descriptive names that reflect the file's purpose.
- Use a consistent case (e.g., camelCase or kebab-case).
- Use appropriate file extensions (e.g.,
.cs,.csproj,.tf,.bicep). - For CSharp components, use
ClassName.csorComponentName.SubComponent.cs.
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.
- 2d ago First seen · 88 lines · 790 tokens per session scan A 204eaca68d1b
solution_architect is a cursor rule published in the GitHub repository Genocs/genocs-library (4 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 790 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-08-31.
Other cursor rules, from other repositories
skill-context-first
Cursor rule "skill-context-first" from TencentBlueKing/bk-ci, covering skill 上下文优先规则, 执行顺序, 默认读取预算, 何时强制先读 skill and 常用路由.
openspec-first
使用 OpenSpec 时，修改代码前必须先更新文档.
graftcode-typescript-node-nextjs
Mandatory Graftcode architecture rules for TypeScript / Node.js / Next.js — expose plain modules via Graftcode instead of REST/gRPC/Thrift.
graftcode-dotnet
Mandatory Graftcode architecture rules for building .NET backend services (class libraries exposed via Graftcode Gateway, not REST).
graftcode-java
Mandatory Graftcode architecture rules for building Java backend services (plain Maven/Gradle modules exposed via Graftcode Gateway, not REST).
game-dev-scrum-master
Game Dev Scrum Master agent (Max).