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/GktuOktay/ai-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/gktuoktay/ai-skills/git-repo-setup)<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/git-repo-setup"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/git-repo-setup/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/gktuoktay/ai-skills/git-repo-setup"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/git-repo-setup.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.00685 |
| Opus 5 | $0.00000 | $0.00342 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
git-repo-setup 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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Repository Setup and Community Standards
This skill covers the best practices for setting up a robust, welcoming, and standardized repository, especially for open-source or team-based projects.
Essential Files
Every professional repository should include the following community health files at its root.
1. README.md
The entry point for the project. It should include:
- Project Name and Description: What it does.
- Badges: CI status, version, license.
- Installation: How to set it up locally.
- Usage: Basic examples of how to use the project.
- Contributing: Link to the contribution guidelines.
- License: The licensing information.
2. CONTRIBUTING.md
Guidelines for how others can contribute to the project.
- How to set up the dev environment.
- Coding standards and conventions.
- How to submit a Pull Request.
- How to report bugs (link to templates).
3. CODE_OF_CONDUCT.md
Establishes expectations for behavior within the community to ensure a welcoming environment. The Contributor Covenant is a widely used standard.
4. LICENSE
Defines how others can use, modify, and distribute the code (e.g., MIT, Apache 2.0, GPL).
Issue and PR Templates
Templates help standardize the information provided by users and contributors. Create them in the .github/ISSUE_TEMPLATE/ and .github/PULL_REQUEST_TEMPLATE.md directories.
- Bug Report Template: Prompts for steps to reproduce, environment, and expected behavior.
- Feature Request Template: Prompts for problem description and proposed solution.
- PR Template: Prompts for description, linked issues, and checklists.
Repository Settings
Configure the repository settings to enforce quality and security.
Branch Protection Rules (for main or master)
- Require Pull Request reviews before merging: Enforce at least 1-2 approvals.
- Require status checks to pass before merging: Ensure CI (tests, linters) passes.
- Require conversation resolution before merging: Ensure all review comments are addressed.
- Require linear history: Prevent merge commits if using squash/rebase strategy.
- Include administrators: Enforce these rules even for repo admins.
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.
- 8d ago First seen · 66 lines · 685 tokens per session scan A 459d14609a61
git-repo-setup is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 685 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-03.
Other cursor rules, from other repositories
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.
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.