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 AmineDjeghri/personal-os-setup --skill repo-conventionsgit clone --depth 1 https://github.com/AmineDjeghri/personal-os-setupWrote 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/aminedjeghri/personal-os-setup/repo-conventions)<a href="https://agentmods.dev/skills/aminedjeghri/personal-os-setup/repo-conventions"><img src="https://agentmods.dev/badge/skills/aminedjeghri/personal-os-setup/repo-conventions/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/aminedjeghri/personal-os-setup/repo-conventions"><img src="https://agentmods.dev/badge/skills/aminedjeghri/personal-os-setup/repo-conventions.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.00069 | $0.00805 |
| Opus 5 | $0.00034 | $0.00402 |
| Sonnet 5 | $0.00014 | $0.00161 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
repo-conventions 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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo conventions (general)
Two layers: universal rules that apply to every repo, and per-repo conventions that differ.
Per-repo specifics live in the repo itself (AGENTS.md / CLAUDE.md / CONTRIBUTING.md / .claude/skills/)
and are auto-loaded when working there — do NOT duplicate them in shared skills.
0. Pre-push checklist (MANDATORY — every repo)
Run BEFORE every push. Skipping these caused real incidents (wrong commit attribution, whole-file diffs, CI rejection).
- Verify git author identity BEFORE committing. GitHub attributes commits by email only; a wrong email links your commit to a different account and pollutes PR participants (unfixable once merged).
- Check:
git config user.name/git config user.email - Email MUST be
<numeric-id>+<username>@users.noreply.github.com— get the id viagh api user -q .id. Never guess (e.g.[email protected]...≠[email protected]). - Fix before pushing:
git commit --amend --author="Real Name <[email protected]>" --no-edit
- Check:
- Run pre-commit on changed files (if
.pre-commit-config.yamlexists):pre-commit run --files <files...>. Hooks must pass; if one auto-fixes, re-add and re-commit. - Conventional commit + conventional PR title. Squash-merge makes the PR title the commit on main; CI often validates it against
(feat|fix|docs|chore|ci|...)(scope)?: .... - Line endings. Repo files may be CRLF while pastes write LF → whole-file diffs. Check:
diff <(git show HEAD:path | tr -d '\r') <(tr -d '\r' < path). Fix with repo-native endings or.gitattributes(doesn't retroactively fix existing blobs). - Force-push etiquette. NEVER force-push without explicit user approval. Prefer
--force-with-leaseover--force. Force-pushing an OPEN PR fixes attribution; a merged PR is frozen.
1. Find the repo's OWN conventions FIRST
Never assume a repo follows another repo's flow. Before committing/pushing/opening a PR in a repo:
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.
- 4d ago First seen · 39 lines · 69 tokens per session scan A 2f68490a459a
repo-conventions is a skill published in the GitHub repository AmineDjeghri/personal-os-setup (602 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 805 once invoked, about $0.0003 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-08.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…