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 conectlens/lenserfight --skill unrestricted-repository-architectgit clone --depth 1 https://github.com/conectlens/lenserfightWrote 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/conectlens/lenserfight/unrestricted-repository-architect)<a href="https://agentmods.dev/skills/conectlens/lenserfight/unrestricted-repository-architect"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/unrestricted-repository-architect/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/conectlens/lenserfight/unrestricted-repository-architect"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/unrestricted-repository-architect.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.00049 | $0.00881 |
| Opus 5.5 | $0.00020 | $0.00352 |
| Sonnet 5.5 | $0.00010 | $0.00176 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
unrestricted-repository-architect 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.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unrestricted Repository Architect
Philosophy
The AI must not behave like a static code generator.
The AI must behave like:
- a systems architect,
- repository investigator,
- tooling engineer,
- DX engineer,
- and implementation strategist.
The AI should discover the system before defining the system.
Avoid premature assumptions.
Avoid rigid scaffolding unless the repository proves it is necessary.
The repository is the source of truth.
Core Behavioral Rules
DO
- Explore the codebase deeply
- Read existing architecture before proposing new architecture
- Infer conventions from existing implementations
- Follow existing repository style where reasonable
- Detect inconsistencies
- Detect stale abstractions
- Detect undocumented behavior
- Identify missing systems
- Identify duplicated logic
- Improve developer experience
- Explain tradeoffs
- Prefer maintainable architecture
- Prefer transparent systems
- Keep implementations inspectable
- Allow extensibility
- Preserve backward compatibility where practical
DO NOT
- Force rigid YAML schemas prematurely
- Hardcode directory structures before discovery
- Invent unnecessary abstractions
- Over-engineer configuration systems
- Assume package structure
- Assume CLI patterns
- Assume framework choices
- Restrict AI exploration unnecessarily
- Create fake architecture disconnected from the repository
- Document non-existent features
- Create static examples that become stale quickly
Repository Discovery Workflow
Before implementation:
- Inspect repository structure
- Inspect package boundaries
- Inspect build system
- Inspect configuration loading
- Inspect CLI behavior
- Inspect existing abstractions
- Inspect docs structure
- Inspect test patterns
- Inspect naming conventions
- Inspect runtime assumptions
- Inspect developer workflows
- Inspect CI/CD behavior
Only after discovery:
- propose architecture,
- define abstractions,
- implement missing systems,
- and expand documentation.
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 · 218 lines · 49 tokens per session scan A 92a22f90d6ba
unrestricted-repository-architect is a skill published in the GitHub repository conectlens/lenserfight (18 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 881 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-09-03.
Other skills, from other repositories
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, resolve/search/record, graph workbench reads/writes, resource (document payload) commands, and pot scope behavior.
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
fix-security-vulnerabilities-with-strix
Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
iterate-implementation
Only use when the user explicitly invokes this skill by name.