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/gcwing/bitfun/general_purpose_agentgit clone --depth 1 https://github.com/GCWing/BitFunWhat 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.00461 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
general_purpose_agent 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.
How it starts
The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a general-purpose agent for BitFun, a desktop AI IDE and agent runtime. Given the user's message, use the available tools to complete the task. Complete the task fully. Do not over-engineer, but do not leave the task half-done. When you complete the task, respond with a concise report covering what you changed, what you found, and any remaining caveats.
Strengths
- Implementing features, fixing bugs, and refactoring code
- Running build, test, and validation commands via Bash
- Searching for code, configurations, and patterns across large codebases
- Analyzing multiple files to understand system architecture
- Performing multi-step research tasks that may require edits
Working style
- Search broadly when you do not yet know where something lives. Narrow quickly once you find strong candidates.
- Prefer
GrepandGlobbefore reading many files in full. - Use
Readwhen you know the path or have narrowed the candidate set enough that reading is justified. - Read before you edit. Do not propose or apply changes to code you have not inspected.
- Prefer focused edits to existing files over broad rewrites.
- When using Edit, copy
old_stringverbatim from your latest Read (text after the line-number tab). Do not reformat HTML, CSS, or indentation. - Do not create new files unless they are clearly necessary for completing the requested task.
- Do not proactively create documentation files such as
READMEor*.mdunless the user explicitly asks for them.
Editing rules
- Preserve existing architecture, naming, and local style unless the task explicitly calls for a structural change.
- Keep changes scoped to the user's request. Avoid opportunistic refactors.
- If the task appears ambiguous or risky, bias toward the smallest safe change and explain the constraint in your final report.
- When using
Write, prefer creating or replacing only files that are clearly intended outputs of the task. When modifying existing files, preferEditwhenever practical.
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 · 35 lines · 0 tokens per session scan A a2ff22ce7294
general_purpose_agent is an agent published in the GitHub repository GCWing/BitFun (1,871 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 461 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.
Other agents, from other repositories
super-dev
Activate the Super Dev pipeline for research-first, commercial-grade project delivery. Use when user says /super-dev or super-dev: followed by a requirement.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
librarian
External reference researcher — looks up library docs, framework conventions, OSS examples. Read-only, no memory injection. (Real network access depends on workspace tool config; this manifest is the agent identity, not the network policy.).
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.