Borrowing it
Nothing to install: this file belongs to web-casa/DeepSeek-Harness-Desktop. 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/web-casa/DeepSeek-Harness-Desktop/main/.agents/skills/asc-ad-hoc-distribution/SKILL.mdgit clone --depth 1 https://github.com/web-casa/DeepSeek-Harness-DesktopWrote 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/web-casa/deepseek-harness-desktop/asc-ad-hoc-distribution)<a href="https://agentmods.dev/skills/web-casa/deepseek-harness-desktop/asc-ad-hoc-distribution"><img src="https://agentmods.dev/badge/skills/web-casa/deepseek-harness-desktop/asc-ad-hoc-distribution/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/web-casa/deepseek-harness-desktop/asc-ad-hoc-distribution"><img src="https://agentmods.dev/badge/skills/web-casa/deepseek-harness-desktop/asc-ad-hoc-distribution.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.00062 | $0.01754 |
| Opus 5 | $0.00031 | $0.00877 |
| Sonnet 5 | $0.00012 | $0.00351 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade B, and why
asc-ad-hoc-distribution scanned grade B with 1 finding 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 12d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 ".asc/distribution/config.json" ".asc/distribution/devices.json" This is a copy
100% identical to asc-ad-hoc-distribution — 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASC ad hoc distribution
Use the experimental asc distribute workflow to turn an existing iOS archive
into a private, verified install link for registered devices. Use TestFlight or
the App Store release skills instead when the build should go through Apple-hosted
distribution.
Confirm the installed contract before acting:
asc distribute --help
asc distribute plan --help
asc distribute apply --help
asc distribute resume --help
asc distribute status --help
asc distribute verify --help
Choose the workflow
- Use
plan->apply->resume/status->verifyfor an end-to-end, hash-authorized run starting from an.xcarchive. - Use
inspect->prepare->publishonly when the caller already owns the ad hoc IPA and wants to operate the lower-level boundaries separately.
Guardrails
- Treat the distribution spec, devices file, PKCS#12 identity, password file, run state, and exact install-link artifact as private. Keep them out of Git and require owner-only permissions.
- Never put S3 credentials or presigned URLs in the distribution spec, command
output, logs, issues, or chat. Use
ASC_S3_ACCESS_KEY_ID,ASC_S3_SECRET_ACCESS_KEY, and optionalASC_S3_SESSION_TOKEN, or the standard AWS SDK credential chain. planis read-only and may exit successfully withready: false. Inspect the typed blockers and effects before continuing.applycan register missing devices, create safe App IDs and successor ad hoc profiles, write local artifacts, and publish immutable objects. Run it only after the user authorizes the exact plan hash and effect inventory.- The orchestrated workflow supports private access to an existing S3-compatible bucket. It does not create buckets, change policies, delete old builds, install the app, or launch it.
- Input drift, an immutable-object conflict, expired signing material, or an expired private link requires a new plan. Do not force the old run forward.
Preconditions
- An existing iOS
.xcarchivewith one main app target. Embedded apps, extensions, Watch apps, and App Clips make the v1 plan not ready. - A local iOS distribution PKCS#12 identity and optional protected password file.
- A protected strict-v1 devices file. For example:
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.
- 12d ago First seen · 190 lines · 62 tokens per session scan B a090ed8e82bc
asc-ad-hoc-distribution is a skill published in the GitHub repository web-casa/DeepSeek-Harness-Desktop (121 stars, last pushed 7d ago), licensed MIT. It adds 62 tokens to every session and 1,754 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 100% identical to asc-ad-hoc-distribution, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
app-release
Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
deployment-rules
Release/deployment standards — semantic-release, commitlint, version sync, the updater. Load for /prepare-release and changes to release.config.mjs / commitlint / workflows / version files. Owned by project-steward.
npm-release
Use when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli. Also use when npm publish fails because of duplicate versions, npm authentication, browser authentication, dist-tag propagation, tarball contents, bin entry issues, or…
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.