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 skills add tuliosousapro/SaaS-blueprint --skill git-controlgit clone --depth 1 https://github.com/tuliosousapro/SaaS-blueprintWrote 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/skills/tuliosousapro/saas-blueprint/git-control)<a href="https://agentmods.dev/skills/tuliosousapro/saas-blueprint/git-control"><img src="https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/git-control/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/skills/tuliosousapro/saas-blueprint/git-control"><img src="https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/git-control.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.00035 | $0.00560 |
| Opus 5.5 | $0.00014 | $0.00224 |
| Sonnet 5.5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
git-control 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Control Skill
When to Use
- Whenever performing version control operations.
- When creating new features, fixing bugs, or managing releases.
- For resolving merge conflicts or recovering from mistakes.
1. Core Workflow
Branching Strategy
- Main Branch: Production-ready code only.
- Feature Branches:
feat/[feature-name]for new functionality. - Bug Fix Branches:
fix/[bug-name]for corrections. - Hotfix Branches:
hotfix/[issue]for urgent production fixes.
Staging & Committing
- Always follow the Conventional Commits skill.
- Stage only relevant changes:
git add <file>(avoidgit add .unless necessary). - Review changes before committing:
git diff --staged.
2. Common Operations
Starting Work
git checkout main
git pull origin main
git checkout -b feat/my-new-feature
Synchronizing
git fetch --all
git pull origin [branch-name]
git push origin [branch-name]
Merging & Rebasing
-
Merge: Use for combining long-lived branches.
-
Rebase: Use to keep feature branches up-to-date with main and maintain a clean history.
git checkout feat/my-feature git rebase main
3. Advanced Git Mastery
Conflict Resolution
- Identify files:
git status. - Edit files to resolve
<<<<,====,>>>>markers. - Stage resolved files:
git add <file>. - Continue:
git commitorgit rebase --continue.
Disaster Recovery
- Undo last commit (keep changes):
git reset --soft HEAD~1. - Undo last commit (discard changes):
git reset --hard HEAD~1. - Find lost commits:
git reflog. - Revert a specific commit:
git revert <commit-hash>.
Stashing
- Save work temporarily:
git stash push -m "work in progress". - Retrieve work:
git stash pop.
4. Quality Gates
- No merge commits on feature branches (prefer rebase).
- Each commit must pass linting and tests.
- Pull requests must be clear and focus on a single objective.
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 · 83 lines · 35 tokens per session scan A 27963f66c58f
git-control is a skill published in the GitHub repository tuliosousapro/SaaS-blueprint (5 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 560 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
ios-appstore-builder
Prepare, configure, and publish iOS apps to the Apple App Store. Covers certificates, provisioning profiles, TestFlight, App Store submission, and review guidelines.
app-release-manager
Manage the complete mobile app release lifecycle from versioning to store submission.
changelog-automator
Professional Changelog Automator Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.
changelog-generator
Professional Changelog Generator Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.
commit-convention
Professional Commit Convention Expert skill. Improve code delivery speed and developer workflows through automation and modern tooling.
release-manager
Professional Release Manager Expert skill. Build robust, automated deployment pipelines and configure cloud infrastructure as code.