Borrowing it
Nothing to install: this file belongs to brake71/1c-ssl-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/brake71/1c-ssl-skills/main/.agents/skills/hosted-agents/SKILL.mdgit clone --depth 1 https://github.com/brake71/1c-ssl-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/brake71/1c-ssl-skills/hosted-agents)<a href="https://agentmods.dev/skills/brake71/1c-ssl-skills/hosted-agents"><img src="https://agentmods.dev/badge/skills/brake71/1c-ssl-skills/hosted-agents/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/brake71/1c-ssl-skills/hosted-agents"><img src="https://agentmods.dev/badge/skills/brake71/1c-ssl-skills/hosted-agents.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.00046 | $0.03401 |
| Opus 5.5 | $0.00018 | $0.01360 |
| Sonnet 5.5 | $0.00009 | $0.00680 |
| Haiku 4.5 | $0.00005 | $0.00340 |
Grade A, and why
hosted-agents 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 17d 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
100% identical to hosted-agents — 0 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.
How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hosted Agent Infrastructure
Hosted agents run in remote sandboxed environments rather than on local machines. When designed well, they provide unlimited concurrency, consistent execution environments, and multiplayer collaboration. The critical insight is that session speed should be limited only by model provider time-to-first-token, with all infrastructure setup completed before the user starts their session.
When to Activate
Activate this skill when:
- Building background coding agents that run independently of user devices
- Designing sandboxed execution environments for agent workloads
- Implementing multiplayer agent sessions with shared state
- Creating multi-client agent interfaces (Slack, Web, Chrome extensions)
- Scaling agent infrastructure beyond local machine constraints
- Building systems where agents spawn sub-agents for parallel work
Do not activate this skill for adjacent work owned by other skills:
- Designing the autonomous research loop, novelty gates, rollback policy, or merge boundaries:
harness-engineering. - Choosing supervisor, swarm, or handoff topology without hosted infrastructure concerns:
multi-agent-patterns. - Designing the tools used by a hosted agent, such as spawn/status tools or PR tools:
tool-design. - Managing file-backed state inside a session rather than the hosted runtime itself:
filesystem-context.
Core Concepts
Move agent execution to remote sandboxed environments to eliminate the fundamental limits of local execution: resource contention, environment inconsistency, and single-user constraints. Remote sandboxes unlock unlimited concurrency, reproducible environments, and collaborative workflows because each session gets its own isolated compute with a known-good environment image.
Design the architecture in three layers because each layer scales independently. Build sandbox infrastructure for isolated execution, an API layer for state management and client coordination, and client interfaces for user interaction across platforms. Keep these layers cleanly separated so sandbox changes do not ripple into clients.
What ships with it
2 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.
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.
- 17d ago First seen · 302 lines · 46 tokens per session scan A 4786dad600b0
hosted-agents is a skill published in the GitHub repository brake71/1c-ssl-skills (82 stars, last pushed 15d ago), licensed MIT. It adds 46 tokens to every session and 3,401 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to hosted-agents, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
web-publish
A publishing tool for making a 1C:Enterprise information base available through Apache, a web server. It creates the 1C web settings, updates Apache configuration, and starts the server.
web-info
A status checker for Apache HTTP Server and 1C web publications. Apache is the web server that makes 1C databases available through browser URLs.
web-stop
A command for stopping Apache HTTP Server, the web server used to expose 1C databases through browser URLs. It stops the server while leaving its web publications configured.
1c-web-info
A status checker for Apache HTTP Server and 1C web publications. It shows whether the server is running, which databases are available through the web, and recent errors.
1c-web-unpublish
A tool for removing a 1C web publication from Apache HTTP Server. A web publication is the configuration that makes a 1C database available through a browser.
1c-web-publish
A setup tool that publishes a 1C information base through Apache HTTP Server so it can be opened in a browser. It creates the web-client configuration, updates Apache, and starts the server.