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 agentmods add agents/ces-ltd/titanx/hello-coder-contextgit clone --depth 1 https://github.com/CES-Ltd/TitanXWhat 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 | $0.00000 | $0.00068 |
| Opus 5 | $0.00000 | $0.00034 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
hello-coder-context 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.
This is a copy
100% identical to hello-coder-context — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Hello Coder Agent
You are a coding agent from the Hello World extension.
Capabilities
- Code generation and refactoring
- Code review and best practices
- Bug identification and fixing
Guidelines
- Write clean, well-documented code
- Follow the project's coding standards
- Explain your reasoning when making 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.
- yesterday First seen · 16 lines · 0 tokens per session scan A 235cb8478706
hello-coder-context is an agent published in the GitHub repository CES-Ltd/TitanX (46 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 68 tokens. A static security scan graded it A with 0 findings. It is 100% identical to hello-coder-context, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
board-workflow
This document describes the end-to-end workflow for AI-assisted issue resolution, from initial issue creation through merged PR.
claude-expression
DISCLAIMER: This document is managed exclusively by Claude Code. The repository admin (AndrewAltimit) does not manage this file and is not allowed to directly edit it. Any updates must come from Claude Code through collaborative sessions.
codebase-analysis-pipeline
This document describes a two-stage automated pipeline for continuous codebase improvement.
pr-monitoring
The PR Monitoring System allows Claude Code to continuously monitor Pull Requests for new comments from administrators and AI reviewers (Claude, OpenRouter, etc.), automatically detecting when responses are needed.
gemini-expression
DISCLAIMER: This document is managed exclusively by Gemini. The repository admin (AndrewAltimit) does not manage this file and is not allowed to directly edit it. Any updates must come from Gemini through code review sessions or collaborative agent interactions.
auto-response
This document describes the automatic response system for AI code review feedback in the GitHub Agents package.