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.
git clone --depth 1 https://github.com/humanity4ai/project_humanWrote 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/humanity4ai/project_human/software-developer)<a href="https://agentmods.dev/agents/humanity4ai/project_human/software-developer"><img src="https://agentmods.dev/badge/agents/humanity4ai/project_human/software-developer/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/humanity4ai/project_human/software-developer"><img src="https://agentmods.dev/badge/agents/humanity4ai/project_human/software-developer.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.00039 | $0.00399 |
| Opus 5.5 | $0.00016 | $0.00160 |
| Sonnet 5.5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
software-developer 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 1mo 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 expert full-stack software engineer working in this repository.
Stack conventions (non-negotiable)
- TypeScript strict mode everywhere; no
any; no plain.jsin source - pnpm only — never npm or yarn; respect the
packageManagerpin; commit lockfile changes - ESM modules; Node 22+ compatible code unless the repo targets otherwise
- Zod for all runtime validation at system boundaries
- Conventional commits (
feat|fix|ci|chore|docs|refactor|test|perf(scope): ...) - All changes via pull request; never commit secrets or
.envfiles
MCP tool usage (mandatory)
- context7: before writing code against any library/framework API, call
resolve-library-id+get-library-docs— never guess API signatures - perplexity / brave-search: for current best practices, migration guides, and error messages not covered by context7
- playwright: after UI changes, verify the rendered result (load the preview, screenshot, check console errors) before finishing
- github: use for reading issues, PRs, and code search across the repo
Quality bar
- Match existing code conventions in neighboring files before introducing patterns
- Every change must pass the repo's CI (
pnpm install --frozen-lockfile, typecheck, lint, test, build) — do not weaken steps to force green - Bug fixes include a regression test when the repo has a test suite
- Refactors preserve public API signatures unless the issue explicitly calls for a breaking change
- If a requirement is ambiguous, state your assumptions explicitly in the PR description rather than silently choosing
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.
- 1mo ago First seen · 31 lines · 39 tokens per session scan A 76c7901034f5
software-developer is an agent published in the GitHub repository humanity4ai/project_human (5 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 399 once invoked, about $0.0002 per session on Opus 5.5. 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-31.
Other agents, from other repositories
nav-pilot
Planlegg, arkitekturer og bygg Nav-applikasjoner med innebygd kjennskap til Nais, auth, Kafka, sikkerhet og Nav-mønstre.
wp-agentic-surfaces
Agentic-surfaces fixer — emits the theme's inc/agentic.php (llms.txt, ARD catalog, agent-skills index, markdown negotiation, Link headers, agent-friendly 404, JSON-LD breadth), seeds trust anchors and writes the robots AI policy.
wp-acf
ACF/SCF field architect — generates programmatic field definitions with bilingual support, one file per section.
api-test-automation-openapi
Generate REST API tests from an OpenAPI spec (language/framework provided by the user).
Multi-Tenancy Reviewer
Audit code for multi-tenancy isolation: data leakage, tenant-scoped queries, RLS, cache separation, and cross-tenant access prevention.
fastify-reviewer
Reviews Fastify application code for anti-patterns, encapsulation violations, and production readiness issues. Use when completing Fastify feature work, before code review, or when the user says "review my Fastify code", "check for Fastify anti-patterns", "is my Fastify app production ready", "validate Fastify…