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/notque/vexjoy-agentWrote 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/commands/notque/vexjoy-agent/github-profile-rules)<a href="https://agentmods.dev/commands/notque/vexjoy-agent/github-profile-rules"><img src="https://agentmods.dev/badge/commands/notque/vexjoy-agent/github-profile-rules/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/commands/notque/vexjoy-agent/github-profile-rules"><img src="https://agentmods.dev/badge/commands/notque/vexjoy-agent/github-profile-rules.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.00529 |
| Opus 5.5 | $0.00000 | $0.00212 |
| Sonnet 5.5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
github-profile-rules 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Profile Rules Pipeline
Domain
github-profile-rules — extract programming rules and coding conventions from a GitHub user's public profile via API.
Agent
github-profile-rules-engineer (new)
- Triggers: github rules, profile analysis, coding style extraction, github conventions, programming rules
- Category: meta
- Complexity: Medium
Skills
github-profile-rules (main orchestration)
- Triggers: github rules, profile analysis, coding style extraction, github conventions, programming rules extraction
- 7-phase pipeline: PROFILE SCAN -> CODE ANALYSIS -> REVIEW MINING -> PATTERN SYNTHESIS -> RULES GENERATION -> VALIDATION -> OUTPUT
- User-invocable: yes
Subdomain Skills
| Skill | Triggers | Task Type |
|---|---|---|
| github-profile-rules-repo-analysis | github repo analysis, code pattern extraction, api repo scanning | analysis |
| github-profile-rules-pr-review | pr review mining, review pattern analysis, developer preference extraction | analysis |
| github-profile-rules-synthesis | rules compilation, pattern deduplication, confidence scoring | analysis |
| github-profile-rules-validation | rules validation, contradiction detection, rule quality check | analysis |
Scripts
| Script | Purpose |
|---|---|
scripts/github-api-fetcher.py |
GitHub REST API client: repos, file contents, PR reviews |
scripts/rules-compiler.py |
Deduplication, confidence scoring, markdown/JSON formatting |
Reference Files
| File | Location |
|---|---|
rule-categories.md |
skills/workflow/references/github-profile-rules/references/ |
Component Graph
github-profile-rules-engineer (agent)
├── github-profile-rules (main skill)
│ ├── references/rule-categories.md
│ ├── invokes: scripts/github-api-fetcher.py
│ └── invokes: scripts/rules-compiler.py
├── github-profile-rules-repo-analysis (subdomain skill)
├── github-profile-rules-pr-review (subdomain skill)
├── github-profile-rules-synthesis (subdomain skill)
└── github-profile-rules-validation (subdomain skill)
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 · 57 lines · 0 tokens per session scan A c23c452bd755
github-profile-rules is a command published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 529 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-08-30.
Other commands, from other repositories
widget-lint
Analyzes SAC custom widget code for performance issues, security concerns, and best practice violations.
api-style-review
Review SAP API style compliance for REST, OData, OpenAPI, SDK naming, documentation, and lifecycle readiness.
btp-architecture-review
Review SAP BTP architecture decisions for account model, services, security, integration, operations, and rollout readiness.
close-the-books
Run the full month-end close - entries, reconciliations, statements, review pack.
review
When reviewing the code changes, the agent should apply general best practices to ensure high code quality. Key areas of evaluation include.
reflect
Have an AI agent critique and improve its own work before delivering it, catching errors and gaps a first pass misses. Run like a /reflect command over a draft, plan, or answer.