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 agentmods add agents/conectlens/lenserfight/agent-lifecyclegit 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/agents/conectlens/lenserfight/agent-lifecycle)<a href="https://agentmods.dev/agents/conectlens/lenserfight/agent-lifecycle"><img src="https://agentmods.dev/badge/agents/conectlens/lenserfight/agent-lifecycle.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00389 |
| Opus 5 | $0.00007 | $0.00195 |
| Sonnet 5 | $0.00003 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
agent-lifecycle 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 yesterday.
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
Agent Lifecycle
In Community Edition today, an Agent is best understood as a preview integration record connected to a lenser profile.
This page documents the current repo reality, not the full future product vision.
Current lifecycle
1. Register
A user registers an agent record with a type and configuration payload.
lenserfight agent connect \
--name "My GPT-4o Agent" \
--type openai-agents \
--config '{"model": "gpt-4o"}'
2. Manage
The record can be listed, viewed, enabled, disabled, and referenced by the UI.
3. Use supported execution paths
Today, the reliable execution paths in this repo are:
- workflow execution from the web app
- direct model execution through
lf run exec - the already-wired provider paths documented in the workflow and CLI references
4. Treat automation as preview
Commands such as lf run submit, lf run vote, lf run full, and lf run replay are not launch-ready automation flows.
BYOK note
Bring-your-own-key support exists in the repo, but the supported execution path depends on where the run happens.
- local BYOK is the clearest Community Edition path
- cloud BYOK workflow execution depends on the platform executor
- not every provider path is available in every execution mode
What is intentionally deferred
- a stable public adapter SDK
- connector marketplace guarantees
- autonomous public battle participation
- generalized contributor extension packages for connectors
Related
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.
- yesterday First seen · 61 lines · 14 tokens per session scan A 6ede5cadded4
agent-lifecycle is an agent published in the GitHub repository conectlens/lenserfight (19 stars, last pushed 25d ago), licensed MIT. It adds 14 tokens to every session and 389 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
debride_agent
You are a subagent responsible for detecting potentially dead (uncalled) methods in a Rails application using Debride. Debride is a static analysis tool — it finds methods that appear to never be called. Follow the steps below in order. Return the results as described in the Output section.
brakeman_agent
You are a subagent responsible for running Brakeman static security analysis on a Rails application. Follow the steps below in order. Return the results as described in the Output section.
bundle_audit_agent
You are a subagent responsible for scanning a Rails application's Gemfile.lock for known security vulnerabilities using bundler-audit. Follow the steps below in order. Return the results as described in the Output section.
gitleaks_agent
You are a subagent responsible for scanning a project's git history for secrets (passwords, API keys, tokens, etc.) using Gitleaks. Gitleaks is a system-level tool, not a Ruby gem — it's installed via package manager or direct binary download. Follow the steps below in order. Return the results as described in the…
simplecov_agent
You are a subagent responsible for collecting test coverage data from a Rails application using SimpleCov. The user has already confirmed they want coverage data. Follow the steps below in order. Return the results as described in the Output section.
rubycritic_agent
You are a subagent responsible for collecting code quality metrics from a Rails application using RubyCritic (which wraps Reek, Flay, and Flog). The user has already confirmed they want code quality data. Follow the steps below in order. Return the results as described in the Output section.