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 agentmods add skills/s3yed/appie-kit/code-qualitynpx skills add S3YED/appie-kit --skill code-qualitygit clone --depth 1 https://github.com/S3YED/appie-kitWhat 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 | $0.00024 | $0.02587 |
| Opus 5 | $0.00012 | $0.01293 |
| Sonnet 5 | $0.00005 | $0.00517 |
| Haiku 4.5 | $0.00002 | $0.00259 |
Grade A, and why
code-quality scanned grade A with 1 finding 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 2d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
os.system(f"ls {user_input}") How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality & Verification
Three complementary tools for ensuring code quality at different stages of development:
| Mode | When | Tool | What it does |
|---|---|---|---|
| Codebase Metrics | Explore/adopt a repo | pygount |
Analyze LOC, language breakdown, code-vs-comment ratios |
| Simplify Code | After implementing changes | 3 parallel subagents | Clean up recent changes for reuse, quality, efficiency |
| Pre-Commit Verification | Before git commit |
Automated pipeline | Security scan, quality gates, independent reviewer, auto-fix |
Section 1: Codebase Metrics (pygount)
Analyze repositories for lines of code, language breakdown, file counts, and code-vs-comment ratios.
When to Use
- User asks for LOC (lines of code) count
- User wants a language breakdown of a repo
- User asks about codebase size or composition
- General "how big is this repo" questions
Prerequisites
pip install --break-system-packages pygount 2>/dev/null || pip install pygount
Basic Summary
cd /path/to/repo
pygount --format=summary \
--folders-to-skip=".git,node_modules,venv,.venv,__pycache__,.cache,dist,build,.next,.tox,.eggs,*.egg-info" \
.
IMPORTANT: Always use --folders-to-skip to exclude dependency/build directories, otherwise pygount will crawl them and hang.
Common Folder Exclusions
# Python projects
--folders-to-skip=".git,venv,.venv,__pycache__,.cache,dist,build,.tox,.eggs,.mypy_cache"
# JavaScript/TypeScript projects
--folders-to-skip=".git,node_modules,dist,build,.next,.cache,.turbo,coverage"
Filter by Language
# Only count Python files
pygount --suffix=py --format=summary .
# Only count Python and YAML
pygount --suffix=py,yaml,yml --format=summary .
Output Formats
pygount --format=summary . # Summary table
pygount --format=json . # JSON for programmatic use
Interpreting Results
The summary table columns: Language, Files, Code (executable lines), Comment (documentation lines), % (percentage of total).
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.
- 2d ago First seen · 298 lines · 24 tokens per session scan A 31dea9dea380
code-quality is a skill published in the GitHub repository S3YED/appie-kit (6 stars, last pushed 6d ago), licensed MIT. It adds 24 tokens to every session and 2,587 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
seo-geo-optimizer
Comprehensive SEO/GEO/AEO analysis toolkit for optimizing content visibility across traditional search engines (Google, Bing), AI platforms (ChatGPT, Perplexity, Claude, Gemini, Grokipedia), answer engines (Google AI Overviews, Bing Copilot, featured snippets), voice assistants (Google Assistant, Siri, Alexa), and…
internal-linking-optimizer
Use when improving internal link structure, anchor text, orphan pages, crawl depth, site architecture, or link equity flow. 内链优化/站内架构.
geo-pipeline
Entry point + orchestrator for the recomby-geo GEO (Generative Engine Optimization) workflow on OpenAI Codex CLI. Use when the user wants to run any stage of the GEO pipeline on a client folder — intake, visibility audit, content-gap analysis, content brief, draft production, distribution, or monthly re-audit — or…
geo-review-html
Render an interactive, self-contained HTML companion for a GEO content brief (04-content-brief) or a publish-ready draft (05-production), so a NON-technical client reviewer (founder, organizer staff, the domain expert filling slots) can fill REQUIRED-FILL slots, leave section-level comments, and approve/return work in…
follow-up-writer
Use when drafting a post-event follow-up message to someone met at a conference.
schedule
Create, list, remove or inspect this bot's scheduled work — recurring jobs ("every morning at 7 tell me X", "every weekday at 9 post the standup") and one-shot follow-ups ("check back in 20 minutes", "watch that deploy until it lands", "remind me on Friday"). Use whenever something must happen on a schedule…