github-profile-rules

A GitHub profile analysis pipeline that examines a developer's public repositories and pull-request reviews to identify coding rules and preferences. It turns repeated patterns into a set of programming conventions.

In plain words
What is it for?
Use it to study repositories, mine pull-request review patterns, extract coding conventions, and compile them into reusable rules.
Why use it?
It helps replace guesswork about someone's coding style with rules based on their public work. Validation checks the generated rules for contradictions and quality.

Command

Install

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.

agentmods
npx agentmods add commands/notque/vexjoy-agent/github-profile-rules
Clone the repo
git clone --depth 1 https://github.com/notque/vexjoy-agent
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 529 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00529
Opus 5 $0.00000 $0.00264
Sonnet 5 $0.00000 $0.00106
Haiku 4.5 $0.00000 $0.00053

Measured yesterday against content hash c23c452bd755, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

commands/github-profile-rules.md · 57 lines

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)

Read the full file on GitHub · 57 lines

Changes

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.

  1. yesterday First seen · 57 lines · 0 tokens per session scan A c23c452bd755

Subscribe to this mod's changes

github-profile-rules is a command published in the GitHub repository notque/vexjoy-agent (417 stars, last pushed 2d ago), 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.