Direct Answer
The strongest repositories in this roundup do not make the model smarter. They make the working environment clearer. I Have ADHD changes how an agent communicates. ECC and HumanLayer encode engineering routines. Ponytail pushes toward smaller implementations. Archify exposes architecture visually. Context Mode keeps bulky tool output outside the conversation. Matt Pocock's skills turn planning and review into repeatable verbs.
That distinction matters. Many agent failures begin as workflow failures: vague requirements, excessive output, hidden architecture, duplicated code, lost context, or a missing review step. A small instruction file can help when the same failure repeats. A plugin becomes more useful when the workflow also needs integrations, commands, scripts, or packaged tools.
Watch the GitHub Roundup
Credit and evidence note: the demonstrations and commentary come from Andrew Warner and Adam Brakhane's episode, published on 11 September 2026. Repository links and supplemental media were organized from the episode's GitHub Show research page. Current repository status was checked on 13 September 2026.
The Repository Map
| Repository | Job | Best first test | Main caveat |
|---|---|---|---|
| I Have ADHD | Concise, action-first output | Compare one troubleshooting answer | Communication preference, not medical guidance |
| ECC | Structured coding-agent process | Run one bounded feature ticket | Large packs can add unused instructions |
| Ponytail | Reduce over-engineering | Review one diff for deletions | Simplicity can become under-building |
| HumanLayer Skills | Reusable engineering loops | Improve one project instruction file | Choose only the relevant skill |
| OpenAI Plugins | Package skills with tools | Inspect one official plugin | More capability means more review |
| Archify | Interactive architecture diagrams | Map one important code path | Validate every claimed connection |
| Context Mode | Externalize large tool results | Compare one log-analysis task | Bad retrieval can erase savings |
| Matt Pocock Skills | Plan, spec, ticket, build, review | Run Grill Me before one feature | The mental model may be enough |
| Humanizer | Remove recurring AI-writing patterns | Edit one draft against a voice sample | Neutral prose is not your voice |
| OpenAI Skills | Historical standalone catalog | Use as migration context | Deprecated; use Plugins |
1. Clearer Output: I Have ADHD
I Have ADHD is a compact skill for changing response shape. It asks the agent to lead with the next action, number steps, cap lists, remove preambles and recaps, and pause when an assumption may be wrong. The before-and-after is the product: less prose between the user and the work.
This is useful when a technically correct agent still creates cognitive overhead. It is also easy to fork because the behavior is visible in one Markdown file. Rename it for a team communication standard if the original framing is not appropriate. The repository does not diagnose ADHD and should not be treated as health guidance.
2. Engineering Discipline: ECC, Ponytail, and HumanLayer
ECC: a broad operating pack
ECC packages agents, commands, skills, rules, and hooks into a fuller engineering environment. That breadth is its advantage and its risk. A new project can gain a shared process quickly, but every extra instruction competes for attention and can age. Audit which components actually run, remove overlaps, and version the chosen configuration with the codebase.
Ponytail: strategic laziness
Ponytail applies a senior-engineer bias toward the smallest adequate change: use what exists, avoid speculative abstractions, and review diffs for code that can disappear. That is valuable because agents are often rewarded for producing visible volume rather than reducing future maintenance.
Better Stack explains Ponytail's decision ladder, caveats, and a side-by-side test. The accompanying Miles Cranmer X post shows why the idea spread. Treat benchmark percentages as claims to reproduce, not guarantees.
HumanLayer: reusable control loops
HumanLayer's skills cover focused jobs such as improving project instructions, narrowing React prop types, building iterated agent loops, and explaining code visually. The useful pattern is not a huge universal prompt. It is a narrow routine with a clear trigger and output. Matt Pocock's show-me recommendation on X is a practical example.
3. OpenAI Plugins Are the Packaging Layer
The episode calls OpenAI Plugins an app store for Codex. The important technical distinction is packaging. A skill can teach a method; a plugin can bundle that method with app connectors, MCP configuration, commands, scripts, agents, hooks, and supporting assets.
OpenAI did not remove skills from Codex. It deprecated the standalone openai/skills catalog and directs users to the plugins repository. Skills remain part of the plugin format. The change says that instructions alone are often not enough for a complete reusable workflow.
Owain Lewis installs and uses a Linear plugin from the Codex plugin marketplace starting at 15:05. The video demonstrates the feature rather than documenting the repository itself.
4. Make Architecture Visible and Context Retrievable
Archify: force a testable picture
Archify turns architecture and workflows into interactive diagrams. A diagram is useful precisely because it is less forgiving than a long explanation: missing boundaries, impossible arrows, and unclear ownership become visible. The repository can map architecture, workflows, sequence, data flow, and lifecycle views.
The demo installs Archify, maps a real code path, inspects architecture diffs, and compares it with other diagram approaches. Also see Voxyz's prompt and install example on X.
Context Mode: move bulk out of the conversation
Context Mode keeps raw tool output in a local searchable layer and returns a smaller result to the agent. The mechanism can help with logs, searches, and large command output. It is not free compression: if the retained summary omits a needed detail, the agent may retrieve the source again and pay for the growing conversation history.
The walkthrough covers context virtualization, session checkpoints, installation, log analysis, and a cost review. Measure the repository against an unchanged control task before accepting headline savings.
5. Matt Pocock Skills and Humanizer
Learn the verb before installing the skill
Matt Pocock's repository turns a development sequence into shared vocabulary: grill the idea, write a spec, create tickets, implement, and review. Grill Me works because it exposes assumptions before code makes them expensive. In many cases, saying "grill me about this plan" is enough. The repository is still useful as a library of mental models and as a consistent team interface.
The Theo recommendation on X focuses on alignment: the agent asks until it has extracted decisions the initial prompt omitted. For larger work, specs and tickets also survive context-window boundaries and allow separate agents to work from the same contract.
Humanizer removes patterns; your voice still needs evidence
Humanizer targets repeated AI-writing habits such as theatrical framing, forced triads, inflated significance, decorative formatting, and chat leftovers. That can make a draft cleaner, but passing an AI detector is not a meaningful editorial standard. Detection tools are unreliable, and generic neutral prose is not the same as a person's voice.
Use the skill as one editing pass after the writer has supplied original ideas, examples, claims, and a real voice sample. The X example discussed in the episode demonstrates the pattern-removal claim; it does not prove authorship.
6. Four Audience Projects Worth Separating From the Top Ten
| Project | What it does | Useful first test |
|---|---|---|
| Reckoner | Combines AI-provider balances and limits in one dashboard | Add one provider and verify warning accuracy |
| Tim Harris Skills | Packages agent workflows for users who do not read code | Run one skill and inspect every generated artifact |
| Clodex | Uses GPT models beneath a Claude Code-style terminal | Compare it with the native Codex harness on one task |
| AI Marketing Panel | Uses simulated customer personas to critique copy | Compare predictions with five real customer interviews |
These projects solve different problems, so star counts do not make a useful ranking. Reckoner is operational visibility. Tim Harris's collection is accessibility. Clodex is model-harness experimentation. AI Marketing Panel is synthetic research. The last category needs the strongest caveat: simulated personas can generate hypotheses, but they cannot replace observations from real customers.
A Seven-Day Repository Test
- Name one failure. Choose verbosity, vague requirements, bloated code, invisible architecture, context overflow, or weak prose.
- Save a control task. Keep the prompt, repository state, model, reasoning level, and acceptance criteria fixed.
- Inspect before installing. Read instructions and scripts; list network, file, shell, credential, and external-app access.
- Run the baseline. Record tokens, elapsed time, retries, changed lines, test results, and reviewer corrections.
- Add one repository. Do not combine several packs while trying to identify the source of improvement.
- Repeat three times. One impressive output may be luck. Look for a stable reduction in rework.
- Keep, fork, or remove. Keep proven behavior, fork what needs tailoring, and delete instructions that do not change outcomes.
Video Chapters
| Time | Topic | Time | Topic |
|---|---|---|---|
| 00:00 | I Have ADHD | 10:17 | Archify |
| 01:40 | ECC engineering process | 11:36 | Context Mode |
| 03:02 | Ponytail | 13:23 | Matt Pocock Skills |
| 05:20 | Zapier MCP | 15:29 | Learning new AI workflows |
| 05:55 | HumanLayer Skills | 16:07 | Humanizer |
| 08:22 | Should the show skip skills? | 17:59 | OpenAI Skills deprecation |
| 08:53 | OpenAI Plugins | 18:54 | Audience submissions |
| 19:28 | Reckoner | 21:34 | AI Marketing Panel |
| 20:05 | Tim Harris Skills | 22:41 | Wrap up |
| 20:36 | Clodex |
Verdict
The useful unit is not the repository. It is the repeated behavior that survives a real test. I Have ADHD is a response contract. Ponytail is a simplicity constraint. Grill Me is a requirements interview. Archify is a visual verification surface. Context Mode is a retrieval strategy. Plugins package those behaviors with the tools needed to execute them.
The episode's debate about whether skills deserve a weekly ranking is healthy. A popular skill may teach a valuable mental model without deserving permanent installation. Start by using the idea in plain language. Package it only when repetition, team consistency, or tool access makes the file valuable.
Source Links
Episode and research page
- The Next New Thing: Top 10 Repos explained
- GitHub Show repository and media research
- Adam Brakhane on LinkedIn
Repositories
- ayghri/i-have-adhd
- affaan-m/ECC
- DietrichGebert/ponytail
- humanlayer/skills
- openai/plugins and deprecated openai/skills
- tt-a1i/archify
- mksglu/context-mode
- mattpocock/skills
- blader/humanizer
Repository behavior, installation methods, licenses, dependencies, and security posture can change. Recheck the current README and source before installation.