Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/kevinnft/ai-agent-skillsnpx agentmods add skills/kevinnft/ai-agent-skills/repo-quality-maksimalisasiWrote 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/kevinnft/ai-agent-skills/repo-quality-maksimalisasi)<a href="https://agentmods.dev/skills/kevinnft/ai-agent-skills/repo-quality-maksimalisasi"><img src="https://agentmods.dev/badge/skills/kevinnft/ai-agent-skills/repo-quality-maksimalisasi/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/kevinnft/ai-agent-skills/repo-quality-maksimalisasi"><img src="https://agentmods.dev/badge/skills/kevinnft/ai-agent-skills/repo-quality-maksimalisasi.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.00025 | $0.02313 |
| Opus 5 | $0.00013 | $0.01156 |
| Sonnet 5 | $0.00005 | $0.00463 |
| Haiku 4.5 | $0.00003 | $0.00231 |
Grade A, and why
repo-quality-maksimalisasi 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.
How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Quality Evaluation & Maksimalisasi
Transform GitHub repos from good (7/10) to perfect (10/10) production-ready state.
When to Use
- User says "gas maksimalkan" or "pastikan perfect"
- Repo needs professional polish for public release
- Want comprehensive CI/CD, tests, and templates
- Preparing repo for community contributions
Quality Scoring Framework
Evaluate across 10 categories (0-10 each):
| Category | Weight | What to Check |
|---|---|---|
| Documentation | 10% | README completeness, examples, architecture docs |
| Installers/Setup | 10% | Automated setup, clear instructions, idempotent |
| Templates | 5% | Starter files, boilerplate, examples |
| CI/CD | 15% | GitHub Actions, automated testing, status badges |
| Examples | 5% | Screenshots, demos, video tutorials |
| Badges | 5% | CI, license, version, stars, forks |
| Changelog | 10% | CHANGELOG.md, semantic versioning, release notes |
| Releases | 10% | GitHub releases, tags, versioned artifacts |
| Issue Templates | 15% | Bug report, feature request, PR templates |
| Tests | 15% | Test suite, coverage, automated validation |
Scoring:
- 0-3: Missing or broken
- 4-6: Basic/minimal
- 7-8: Good/functional
- 9-10: Excellent/comprehensive
Total Score = Average of all categories
Maksimalisasi Workflow
Phase 1: CHANGELOG + Release (15 min)
-
Create CHANGELOG.md
cat > CHANGELOG.md << 'EOF' # Changelog ## [1.1.0] - YYYY-MM-DD ### Added - Feature A - Feature B ## [1.0.0] - YYYY-MM-DD ### Added - Initial release EOF -
Create GitHub release
git tag -a v1.1.0 -m "v1.1.0 - Description" git push origin v1.1.0 gh release create v1.1.0 --title "v1.1.0 - Title" --notes "Release notes"
Phase 2: Badges + FAQ (20 min)
- Add badges to README
[](https://github.com/owner/repo/actions) [](https://opensource.org/licenses/MIT) [](https://github.com/owner/repo/releases) [](https://github.com/owner/repo/stargazers) [](https://github.com/owner/repo/network/members)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 318 lines · 25 tokens per session scan A 80df3e4eceec
repo-quality-maksimalisasi is a skill published in the GitHub repository kevinnft/ai-agent-skills (14 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 2,313 once invoked, about $0.0001 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-03.
Other skills, from other repositories
pdlc-ship
A software release workflow that runs tests, updates the version and change log, creates a Git tag, and starts CI/CD, the automated build and deployment process.
actions-reusable-workflows
Wire a repository to the bitwise-media-group/github-workflows reusable workflows — thin, SHA-pinned caller workflows for CI, security (CodeQL) scanning, release (release-please/GoReleaser/Zensical docs), the signature-preserving fast-forward /merge + merge-review-ack + merge-notice flows, and add-to-project — plus the…
update-downstream-packages
Use when rolling a newly published package release through every maintained consumer repository and verifying CI.
trusted-publish
Publish a package from a git repo to its registry via OIDC Trusted Publishing — no long-lived tokens. Writes the GitHub Actions publish workflow, walks the user through the registry-side trust entry, releases, and verifies. Use when the user wants to publish or release a package to PyPI, npm, crates.io, or another…
production-release-gating
Stop every push/merge to main from shipping to production — deploy only on a real release. Use when a merge to main unexpectedly deploys to prod, when you want production to deploy only on a semantic-release version (not every commit), when setting up preview-on-feature-branch but gated-prod-on-main, wiring a Vercel…
github-cli
Apply when using the gh CLI to manage pull requests, issues, releases, or CI workflows on GitHub.