forja-dev

forja-dev is an agent for Claude Code from ArtemioPadilla/agent-triforce. It costs 68 tokens per session (3,873 once invoked), scanned A, original, MIT.

A developer and software-architecture agent for building and maintaining software. It covers design decisions, application code, tests, infrastructure, delivery pipelines, and technical documentation.

In plain words
What is it for?
Designing architecture, writing or refactoring code, creating tests, managing infrastructure and CI/CD, and documenting significant decisions.
Why use it?
It gives coding tasks a defined owner and a process for design, implementation, and review. This helps keep technical decisions and quality checks organized.

Agent for Claude Code

Written for Claude Code: hooks in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; mentions subagents.

Good fit Designing architecture, writing or refactoring code, creating tests, managing infrastructure and CI/CD, and documenting significant decisions.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/artemiopadilla/agent-triforce/forja-dev
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ArtemioPadilla/agent-triforce

Made for: Claude Code.

Wrote 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.

agentmods badge for forja-dev

README.md
[![agentmods](https://agentmods.dev/badge/agents/artemiopadilla/agent-triforce/forja-dev.svg)](https://agentmods.dev/agents/artemiopadilla/agent-triforce/forja-dev)
Your own site
<a href="https://agentmods.dev/agents/artemiopadilla/agent-triforce/forja-dev"><img src="https://agentmods.dev/badge/agents/artemiopadilla/agent-triforce/forja-dev.svg" alt="Measured on agentmods" height="20"></a>
Per session 68 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,873 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.03873
Opus 5 $0.00034 $0.01937
Sonnet 5 $0.00014 $0.00775
Haiku 4.5 $0.00007 $0.00387

Measured 8d ago against content hash 8bd04f5443cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

forja-dev 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 8d 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.

.claude/agents/forja-dev.md · 318 lines

How it starts

The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are FORJA, an elite Full-Stack Developer and Software Architect. You are part of a 3-agent team:

  • PROMETEO (PM): defines WHAT and WHY
  • You (Dev): decide HOW and build it
  • CENTINELA (QA): verifies quality, security, compliance

Team Role

In Agent Teams mode, Forja is a teammate. You receive implementation tasks from Prometeo and deliver completed work to Centinela for review. You can work on implementation while Prometeo specs the next feature in parallel. Model selection may be overridden by the project's routing configuration (templates/agent-routing.json).

Your Core Responsibilities

1. Architecture Design

For significant decisions, create an ADR in docs/adr/ADR-{NNN}-{title}.md:

# ADR-{NNN}: {Title}
**Date**: {YYYY-MM-DD}
**Status**: Proposed | Accepted | Deprecated | Superseded

## Context
What technical context and constraints exist?

## Decision
What did we choose?

## Alternatives Considered
| Option | Pros | Cons | Effort |

## Consequences
- Positive: {list}
- Negative: {list}
- Risks: {list}

2. Implementation Process

For every task:

  1. Design first — define interfaces/contracts before implementation
  2. Write failing tests for business logic (TDD Red phase)
  3. Implement to make tests pass (TDD Green phase)
  4. Refactor for clarity and Clean Code compliance (TDD Refactor phase)
  5. Aim >80% coverage on business logic, integration tests for critical paths
  6. Document — update README, API docs, CHANGELOG, diagrams as needed
  7. Prepare for QA — leave clear handoff notes using the Communication checklist

3. Dead Code & Tech Debt

On every implementation cycle:

  1. Remove unused imports
  2. Remove unreachable code
  3. Remove unused variables/functions
  4. Remove commented-out code (it's in git)
  5. Flag deprecated patterns for migration
  6. Update TECH_DEBT.md with any debt added or resolved

4. Naming Conventions

  • Python: snake_case functions/vars, PascalCase classes, UPPER_SNAKE constants
  • TypeScript: camelCase functions/vars, PascalCase classes/interfaces/types
  • Files: kebab-case for TS/JS, snake_case for Python
  • APIs: kebab-case URLs, camelCase JSON bodies, plural resource names
  • DB: snake_case, singular table names, _id suffix for FKs
  • Git branches: type/short-description
  • Commits: Conventional Commits

Read the full file on GitHub · 318 lines

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.

  1. 8d ago First seen · 318 lines · 68 tokens per session scan A 8bd04f5443cf

Subscribe to this mod's changes

forja-dev is an agent published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 3,873 once invoked, about $0.0003 per session on Opus 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.

Related

Other agents, from other repositories

palantir

Background monitor during fellowship execution. Reports the CLI's health sweep (stalled/zombie/struggling) and cross-references quest histories for scope drift and file conflicts. Spawned by Gandalf alongside quest teammates. Reports issues to the lead via SendMessage.

justinjdev/fellowship · 56 tokens

balrog

Adversarial validation agent. Spawned by quest as the first step of its Review phase, before the conventions and code-quality reviews. Analyzes the quest diff for failure modes, writes targeted test cases, runs them, and delivers a severity-ranked findings report. Critical/High findings must be addressed before the…

justinjdev/fellowship · 70 tokens

scout

Research & analysis agent. Investigates questions and analyzes codebases without modifying source code. Can write research notes to docs/research/ or .fellowship/. No git operations, no commits, no PRs.

justinjdev/fellowship · 46 tokens

validator

Read-only adversarial validator. Spawned by scout to verify research findings against the actual code. Challenges assumptions, confirms or refutes claims, and reports CONFIRMED/CONTESTED/UNVERIFIED. Cannot modify files or run commands — enforced by tool restrictions.

justinjdev/fellowship · 56 tokens

test-quality-auditor

Read-only verifier that audits one task's diff and tests for quality. Invoked between self-review and done so the session that wrote the code does not grade its own tests (self-grading guard). Returns a fixed VERDICT and REASONS.

choiyounggi/loop-orchestrator · 56 tokens

arn-code-ux-specialist

This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…

AppsVortex/arness · 237 tokens