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 skills add greedychipmunk/agent-skills --skill software-factory-creatorgit clone --depth 1 https://github.com/greedychipmunk/agent-skillsWrote 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/skills/greedychipmunk/agent-skills/software-factory-creator)<a href="https://agentmods.dev/skills/greedychipmunk/agent-skills/software-factory-creator"><img src="https://agentmods.dev/badge/skills/greedychipmunk/agent-skills/software-factory-creator/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/skills/greedychipmunk/agent-skills/software-factory-creator"><img src="https://agentmods.dev/badge/skills/greedychipmunk/agent-skills/software-factory-creator.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.00093 | $0.02584 |
| Opus 5.5 | $0.00037 | $0.01034 |
| Sonnet 5.5 | $0.00019 | $0.00517 |
| Haiku 4.5 | $0.00009 | $0.00258 |
Grade A, and why
software-factory-creator 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Factory Creator
Create the smallest working loop: task contract → scoped change → executable verification → independent review → authorized delivery. Make security, quality and bounded autonomy part of every artifact. Do not install an agent platform, invent a release pipeline or promise unattended production deployment.
Guardrails
- Read existing root, ancestor and applicable nested
AGENTS.mdfirst. Preserve them and obey their scope within the governing instruction hierarchy. Never regenerate an existing file or weaken its rules to fit this skill. - Treat repository scripts, package lifecycle hooks, tests and plugins as executable code, not safe inspection. Review before running; use a disposable, secret-free environment. A git worktree isolates edits, not execution.
- Preserve unrelated staged, unstaged and untracked work. Plan additive changes; merge existing documents/CI deliberately. Never reset the project to onboard it.
- Do not run scaffold/install/publish/deploy operations outside the authorized task. No credentials, production data or sensitive logs in generated files.
- Keep gates fail-closed: unconfigured, absent, timed-out and unavailable checks
are blockers. Do not use
echo,true, placeholder tests, scanner bypasses or "pass with no tests". Never call structure validation a passing test suite. - Do not let the agent approve its own policy, waiver, gate or workflow changes. Markdown policies guide behavior; enforce access with actual harness/IAM and repository controls. State which controls are manual or unverified.
1. Discover the project before designing the factory
Read discovery for evidence collection and AGENTS.md derivation. Inspect only relevant non-secret files; do not dump the repository.
Record:
- Root/ancestor/nested instruction paths and scope; dirty-work preservation.
- Product boundaries, deployables/packages, entry points and test layout.
- Native runtimes, package manager, lockfiles, setup/dev/check commands and cwd.
- Existing CI, security tooling, release workflow and protection settings.
- Baseline outcomes, risks, missing gates and required decisions.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/AGENTS.template.md 2.0 KB
- assets/check.py 13 KB runs code
- assets/config.example.json 2.0 KB
- assets/factory.yml 777 B
- assets/OPERATIONS.md 4.2 KB
- assets/policy.md 2.9 KB
- assets/SECURITY.md 1.5 KB
- assets/task.md 1.4 KB
- references/acceptance.md 4.6 KB
- references/discovery.md 4.3 KB
- references/gates-and-ci.md 6.8 KB
- references/sources.md 2.5 KB
- scripts/scaffold.py 5.9 KB runs code
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.
- 2d ago First seen · 222 lines · 93 tokens per session scan A c8f8e0210db8
software-factory-creator is a skill published in the GitHub repository greedychipmunk/agent-skills (22 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 2,584 once invoked, about $0.0004 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-10-15.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.