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 skills add Ruisi-Lu/github-loop-engineering-skill --skill project-quizgit clone --depth 1 https://github.com/Ruisi-Lu/github-loop-engineering-skillWrote 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/ruisi-lu/github-loop-engineering-skill/project-quiz)<a href="https://agentmods.dev/skills/ruisi-lu/github-loop-engineering-skill/project-quiz"><img src="https://agentmods.dev/badge/skills/ruisi-lu/github-loop-engineering-skill/project-quiz/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/ruisi-lu/github-loop-engineering-skill/project-quiz"><img src="https://agentmods.dev/badge/skills/ruisi-lu/github-loop-engineering-skill/project-quiz.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.00071 | $0.01615 |
| Opus 5.5 | $0.00028 | $0.00646 |
| Sonnet 5.5 | $0.00014 | $0.00323 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
project-quiz 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Read GitHub only through the connected GitHub MCP server. Don't fall back to `gh`, `curl`, direct REST, or handwritten GraphQL. If no GitHub MCP server is connected, or it can't read pull requests, stop and say which How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project quiz
Turn a repository's pull request history into a short quiz that teaches the project. Merged pull requests record what changed, why, which alternatives were rejected, and which bugs shaped the current design. Reading them all is slow, so you read them, pick what a collaborator most needs to know, and ask about it. Every answer, right or wrong, is followed by a short explanation with the pull request it came from.
The quiz is for learning, not for grading. A wrong answer means the next explanation matters, never that the user failed.
Rules
- Start only when the user invokes this skill or explicitly asks for a project quiz. Never start one as a side effect of other work.
- Read GitHub only through the connected GitHub MCP server. Don't fall back to
gh,curl, direct REST, or handwritten GraphQL. If no GitHub MCP server is connected, or it can't read pull requests, stop and say which toolset or permission is missing. Thepull_requests,issues, andrepostoolsets cover everything this skill reads. - Write nothing to GitHub: no comments, labels, issues, or reviews. The quiz stays in the conversation. Save it to a local file only when the user asks, at a path they choose.
- Ground every question in evidence you read: a pull request, its closing issues, its review discussion, or the current code. Never invent a reason a pull request doesn't state. When the history doesn't say why, ask about what changed, not why.
- Leave people out. Don't ask who wrote, reviewed, or merged something, and don't judge anyone's work.
- Never put a secret, credential, internal hostname, or personal data from a diff or discussion into a question or an explanation, even in a private repository.
1. Settle the scope
Take the scope from the invocation's arguments and the conversation. Use these defaults for anything not given, and don't ask about them:
- Repository: the current repository, from the git remote or the conversation. When more than one is plausible, ask one question.
- Questions: 8.
- Range: the most recently merged pull requests, as many as you need to find enough material. Go back further when recent history is mostly routine.
- Area: the whole project, unless the user names a directory, component, label, or date range.
- Language: the user's language. Keep code, commands, and identifiers as they are.
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.
- 5d ago First seen · 80 lines · 71 tokens per session scan A f1bfa2fa905a
project-quiz is a skill published in the GitHub repository Ruisi-Lu/github-loop-engineering-skill (8 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,615 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-01.
project-quiz compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| project-quizRuisi-Lu/github-loop-engineering-skill | Skill | 8 | yesterday | MIT | A | 71 | Claude Code |
| moai-ref-git-workflowmodu-ai/moai-adk | Skill | 1.3k | 4d ago | Apache-2.0 | A | 58 | Claude Code |
| request-apexyard-featureme2resh/apexyard | Skill | 542 | yesterday | MIT | A | 47 | Claude Code |
| changelogwesammustafa/Claude-Code-Everything-You-Need-to-Know | Skill | 3.5k | 3d ago | none | A | 28 | Claude Code |
| git-workflowNPC-Worldwide/npcsh | Skill | 502 | 3d ago | MIT | A | 0 | Claude Code, Codex |
| signing-preflightavelikiy/great_cto | Skill | 112 | 2d ago | MIT | A | 105 | Claude Code |
| validate-changesFlorianBruniaux/claude-code-ultimate-guide | Skill | 6.4k | 2d ago | CC-BY-SA-4.0 | A | 16 | Claude Code |