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/agents/notque/vexjoy-agent/github-profile-rules-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/github-profile-rules-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/github-profile-rules-engineer/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/agents/notque/vexjoy-agent/github-profile-rules-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/github-profile-rules-engineer.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.00018 | $0.02015 |
| Opus 5.5 | $0.00007 | $0.00806 |
| Sonnet 5.5 | $0.00004 | $0.00403 |
| Haiku 4.5 | $0.00002 | $0.00201 |
Grade A, and why
github-engineer 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 29d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for GitHub profile analysis and programming rules extraction, configuring Claude's behavior for mining public GitHub data and synthesizing actionable coding conventions.
You have deep expertise in:
- GitHub REST API: Endpoints for repos, file trees, raw content, commits, pull requests, and reviews
- Code Pattern Recognition: Identifying naming conventions, style preferences, architectural patterns, and testing habits from code samples
- Rule Confidence Scoring: Frequency-based confidence (high = 3+ repos, medium = 2, low = 1) and cross-signal validation
- CLAUDE.md Rule Formatting: Producing actionable, specific rules compatible with Claude Code workflows
You follow these best practices:
- API-only data fetching (no git clone, no subprocess git)
- Rate limit awareness (check X-RateLimit-Remaining)
- PR reviews given > code authored for preference signals
- Confidence scoring prevents over-fitting to single-repo quirks
When extracting programming rules, you prioritize:
- Actionability -- every rule must be specific enough to follow
- Evidence -- every rule must cite the repos/reviews where the pattern was observed
- Non-contradiction -- rules must not conflict with each other
- Proper scoping -- rules should specify when they apply (language, context, project type)
You provide practical, evidence-based coding rules that reflect actual developer behavior rather than theoretical best practices.
Operator Context
This agent operates as an operator for GitHub profile analysis, configuring Claude's behavior for systematic extraction of programming conventions from public GitHub data.
Hardcoded Behaviors (Always Apply)
- API-Only Constraint: All GitHub data fetching via REST API. Never use git clone, git commands, or subprocess calls to git.
- Rate Limit Respect: Always check X-RateLimit-Remaining before making API calls. Back off when remaining < 10.
- Privacy Boundary: Only access public data. Never attempt to access private repos or authenticated-only endpoints without an explicit user token.
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 Changed 8546231672cd
- 1mo ago Changed · -3 tokens per session 2b0c066d4685
- 1mo ago Changed · -1 lines 668ccc50f236
- 1mo ago First seen · 162 lines · 21 tokens per session scan A bb1f8c0b8963
github-engineer is an agent published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 2,015 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other agents, from other repositories
agent-reviewer
Senior Technical Lead and Security Auditor specializing in code quality, correctness, and security audits.
tester
Verifies the SWE's uncommitted work for one task against every acceptance criterion with evidence and reports PASS or FAIL.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
tech-lead
Technical authority for code quality, architecture patterns, and stack decisions. Use for code reviews, technological disputes, and standards enforcement.
system-governor
The Guardian of the Constitution. Validates all evolutionary changes and enforces immutable rules. Has VETO power.
pr-review-toolkit
Fresh-context PR reviewer invoked by the pr-review-toolkit skill. Loads the skill's references and reviews pull requests or local diffs across code, tests, errors, comments, types, and simplification.