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/dstotijn/mcp-cbs-cijfers-open-dataWrote 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/dstotijn/mcp-cbs-cijfers-open-data/go-project-structure)<a href="https://agentmods.dev/rules/dstotijn/mcp-cbs-cijfers-open-data/go-project-structure"><img src="https://agentmods.dev/badge/rules/dstotijn/mcp-cbs-cijfers-open-data/go-project-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/dstotijn/mcp-cbs-cijfers-open-data/go-project-structure"><img src="https://agentmods.dev/badge/rules/dstotijn/mcp-cbs-cijfers-open-data/go-project-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.00702 |
| Opus 5 | $0.00000 | $0.00351 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
go-project-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 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.
This is a copy
86% identical to go-project-structure — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description
This rule ensures that Go projects follow a consistent and idiomatic structure, making the codebase easier to navigate, maintain, and scale.
Rule
When organizing a Go project:
Directory Structure
-
Use the standard Go project layout:
/cmd- Main applications for this project/internal- Private application and library code/pkg- Library code that's ok to use by external applications/api- API definitions, protocol buffers, OpenAPI/Swagger specs/web- Web application specific components/configs- Configuration file templates or default configs/scripts- Scripts to perform various build, install, analysis, etc. operations/test- Additional external test apps and test data
-
Place main application entry points in
/cmd/<appname>directories -
Keep internal code that shouldn't be imported by other projects in
/internal -
Place shared libraries that can be imported by other projects in
/pkg
Package Organization
- Organize packages by functionality, not by type
- Keep package names short, clear, and descriptive
- Avoid package name collisions with standard library
- Use singular form for package names (e.g.,
store, notstores) - Avoid deeply nested package hierarchies
Dependency Management
- Use Go modules for dependency management
- Pin dependencies to specific versions in go.mod
- Regularly update and audit dependencies
- Minimize the number of external dependencies
- Prefer standard library solutions when available
Configuration
- Use environment variables for configuration
- Support configuration files as an alternative
- Provide sensible defaults for all configuration options
- Validate configuration at startup
Testing
- Place tests in the same package as the code they test
- Use
_test.gosuffix for test files - Place integration tests in a separate
integrationpackage - Store test fixtures in
testdatadirectories
Implementation
- The Cursor IDE will enforce this rule by:
- Suggesting appropriate locations for new files
- Highlighting structural issues
- Providing refactoring options to improve project organization
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 · 101 lines · 702 tokens per session scan A ce7ac4d2fca9
go-project-structure is a cursor rule published in the GitHub repository dstotijn/mcp-cbs-cijfers-open-data (8 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 702 tokens. A static security scan graded it A with 0 findings. It is 86% identical to go-project-structure, differing in 16 lines, and is treated as a copy.
Other cursor rules, from other repositories
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
code-style
Formatting, lint, comments language.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
go-conventions
Go conventions for all Go code (modules, naming, errors, logging, metrics).
go-grpc-service-rule
A set of Chinese-language rules for implementing gRPC services in Go. gRPC is a way for software services to communicate using defined messages and procedures.