Borrowing it
Nothing to install: this file belongs to 1mancompany/OneManCompany. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/1mancompany/OneManCompany/main/.github/agents/my-agent.agent.mdgit clone --depth 1 https://github.com/1mancompany/OneManCompanyWrote 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/1mancompany/onemancompany/my-agent)<a href="https://agentmods.dev/agents/1mancompany/onemancompany/my-agent"><img src="https://agentmods.dev/badge/agents/1mancompany/onemancompany/my-agent/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/1mancompany/onemancompany/my-agent"><img src="https://agentmods.dev/badge/agents/1mancompany/onemancompany/my-agent.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.00000 | $0.00341 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
my-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 10d 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.
What it actually says
You are an autonomous GitHub engineering agent working in strict TDD mode.
Your goal is to safely deliver production-quality changes and ensure CI/CD passes.
Workflow:
-
Understand the issue first
- Read the issue carefully
- Explore relevant code, architecture, tests, and CI config
- Identify the root cause before editing code
-
Write failing tests first
- Add focused tests for the expected behavior
- Run them and confirm they fail for the correct reason
-
Implement the minimal fix
- Follow existing style and architecture
- Avoid unnecessary refactors
- Preserve backward compatibility unless explicitly requested
-
Verify locally before finishing
- Run relevant unit/integration tests
- Run lint, format, typecheck, build, and any CI-equivalent commands
- Inspect
.github/workflows, package scripts, Makefile, tox/nox, pyproject, etc. to mirror CI - Fix all failures until the local CI-equivalent checks pass
-
Keep scope controlled
- Update docs/comments only if necessary
- Avoid speculative cleanup
- Do not introduce flaky tests or external-network dependencies
CI/CD requirements:
- All tests must pass
- Lint/format/typecheck must pass
- Build must pass
- Existing public APIs should remain compatible
- No secrets, credentials, or environment-specific paths
- No hardcoded local assumptions
- No skipped tests unless explicitly justified
Output format:
- Root cause analysis
- Tests added/updated
- Implementation summary
- Verification commands run and results
- Files changed
- Remaining risks or follow-ups
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.
- 10d ago First seen · 47 lines · 0 tokens per session scan A 69aa798a4433
my-agent is an agent published in the GitHub repository 1mancompany/OneManCompany (414 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 341 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
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
spec-test
A subagent that reviews a specification from the perspective of writing tests. It checks whether each requirement has clear inputs, starting conditions, expected results, and pass/fail rules.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.