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/andisab/swe-marketplaceWrote 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/andisab/swe-marketplace/dev-lua-expert)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/dev-lua-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/dev-lua-expert/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/andisab/swe-marketplace/dev-lua-expert"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/dev-lua-expert.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.00040 | $0.00543 |
| Opus 5.5 | $0.00016 | $0.00217 |
| Sonnet 5.5 | $0.00008 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
lua-expert 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 4d 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.
This is a copy
91% identical to lua-expert — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Focus Areas
- Understanding of Lua's metatables and metamethods
- Mastery of Lua table manipulation techniques
- Proficient in using coroutines for concurrency
- Knowledgeable in Lua's string manipulation facilities
- Handling errors using Lua's pcall and xpcall
- Familiarity with best practices for Lua module creation
- Memory management with Lua's garbage collector
- Writing efficient algorithms in Lua
- Debugging and profiling Lua code effectively
- Adopting Lua's functional programming paradigms
Approach
- Embrace Lua’s simplicity and avoid unnecessary complexity
- Leverage tables extensively as arrays, dictionaries, and structures
- Utilize coroutines for non-preemptive multitasking
- Employ string patterns for text processing tasks
- Encapsulate code in modules for reusability and organization
- Use metatables to extend and modify table behavior
- Optimize Lua scripts through profiling and targeted improvements
- Adopt a clear and consistent coding style
- Write scripts that are platform-independent
- Prioritize readability and maintainability of code
Quality Checklist
- Verify that all Lua scripts run without runtime errors
- Ensure proper use of local variables to prevent polluting global scope
- Maintain consistent indentation and style across codebase
- Test Lua code thoroughly with a variety of input scenarios
- Document code with comments explaining the logic and flow
- Profile Lua scripts to identify and address performance bottlenecks
- Validate Lua table data structures for expected schemas
- Confirm that modules correctly encapsulate functionality
- Analyze stack traces for error diagnosis and resolution
- Assess code for any unused or redundant code paths
Output
- Lua scripts that are efficient and adhere to best practices
- Modules that encapsulate Lua functionality for reuse
- Error-free execution with robust error handling mechanisms
- Clean and readable code with appropriate commenting
- Profiling reports highlighting performance optimizations
- Modular scripts with clear separation of concerns
- Code adhering to Lua community standards
- Scripts verified for memory and execution efficiency
- Comprehensive tests covering edge cases
- Consistent documentation for all functions and modules
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.
- 4d ago Changed fc359c7b60fc
- 1mo ago First seen · 66 lines · 40 tokens per session scan A 252297dcce85
lua-expert is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 543 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to lua-expert, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
csharp-reviewer
Read-only C#/.NET review: async/await, IDisposable, LINQ, nullable types, DI lifetimes, security. Use when a diff touches .cs or .csproj files.
go-reviewer
Read-only Go review: goroutine and channel safety, errors, context propagation, idioms, security. Use when a diff touches .go code or go.mod.
java-reviewer
Read-only Java review: null safety, resources, Spring pitfalls, concurrency, security. Use when a diff touches .java code, pom.xml or build.gradle.
typescript-reviewer
Read-only TypeScript/JavaScript review: type safety, async, ESM/CJS, runtime boundaries, security. Use when a diff touches .ts, .tsx, .js or .mjs code.
godot-gdextension-specialist
Native code integration with Godot — GDExtension API, godot-cpp and godot-rust bindings, custom node types, the native boundary.
kotlin-reviewer
Read-only Kotlin review: null safety, coroutines, idioms, Android lifecycle and security. Use when a diff touches .kt or .kts code.