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 SteelMorgan/1c-agent-based-dev-framework --skill dap-bsl-code-debug-proceduregit clone --depth 1 https://github.com/SteelMorgan/1c-agent-based-dev-frameworkWrote 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/steelmorgan/1c-agent-based-dev-framework/dap-bsl-code-debug-procedure)<a href="https://agentmods.dev/skills/steelmorgan/1c-agent-based-dev-framework/dap-bsl-code-debug-procedure"><img src="https://agentmods.dev/badge/skills/steelmorgan/1c-agent-based-dev-framework/dap-bsl-code-debug-procedure/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/steelmorgan/1c-agent-based-dev-framework/dap-bsl-code-debug-procedure"><img src="https://agentmods.dev/badge/skills/steelmorgan/1c-agent-based-dev-framework/dap-bsl-code-debug-procedure.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.00026 | $0.02273 |
| Opus 5 | $0.00013 | $0.01137 |
| Sonnet 5 | $0.00005 | $0.00455 |
| Haiku 4.5 | $0.00003 | $0.00227 |
Grade A, and why
dap-bsl-code-debug-procedure 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 6d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 6d ago First seen · 166 lines · 26 tokens per session scan A aa7bcef04a33
dap-bsl-code-debug-procedure is a skill published in the GitHub repository SteelMorgan/1c-agent-based-dev-framework (99 stars, last pushed 2mo ago), with no licence file. It adds 26 tokens to every session and 2,273 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 skills, from other repositories
bsl-diagnostic-rule-development
Semantic workflow for implementing, reviewing, or fixing onec-hbk-bsl diagnostic rules. Use for BSL/1C rule semantics, CST or tree-sitter behavior, BSLLS parity, performance, synthetic fixtures, related-rule overlap, and questions about whether a rule matches its documented language behavior.
ai-edt
1C:Enterprise development through the AI-EDT MCP server - BSL analysis and editing, metadata and managed forms, query validation, project diagnostics, debugging, infobase updates and unit tests. Use when the project is a 1C:EDT workspace: BSL modules, .mdo metadata, 1C queries, managed forms. Also use when all you…
dotnet-reverse
A guide for analyzing compiled .NET and C# programs, including managed Windows executables and libraries. Reverse engineering means studying compiled software to understand how it works, and decompiling turns it back into readable approximate source code.
dart-run-static-analysis
Execute dart analyze to identify warnings and errors, and use dart fix --apply to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.
agents-sdk-dotnet-debugging
Use when troubleshooting an agent built with the Microsoft Agents SDK (Microsoft.Agents.Hosting.AspNetCore and related packages) in C# / .NET. Trigger on any of these symptoms: build or C# compile errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, appsettings.json…
golang-error-handling
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log…