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 skills/jinning6/noosphere/docker-git-bind-mount-push-debugnpx skills add JinNing6/Noosphere --skill docker-git-bind-mount-push-debuggit clone --depth 1 https://github.com/JinNing6/NoosphereWhat 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.00078 | $0.00623 |
| Opus 5 | $0.00039 | $0.00311 |
| Sonnet 5 | $0.00016 | $0.00125 |
| Haiku 4.5 | $0.00008 | $0.00062 |
Grade A, and why
docker-git-bind-mount-push-debug 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Git Bind-Mount Push Debug
Separate the control plane, container lifecycle, Git trust, remote addressing, mount policy, and outcome verification. Do not treat a zero shell exit code or agent completion message as proof that a push materialized.
Diagnose In Order
- Inspect the exact
docker runarguments. Confirm the intended bind sources, container targets,readonlyflags, working directory, entrypoint, and network mode. - Confirm the container stays alive across multiple
docker execcalls. Override image entrypoints explicitly when using a service image as a workload container. - Inside the container, register every bind-mounted Git object that Git will open:
git config --global --add safe.directory /workspace/repo
git config --global --add safe.directory /workspace/approved.git
git config --global --add safe.directory /workspace/unauthorized.git
Trusting only the worktree is insufficient when git push opens a bind-mounted bare remote.
- Configure remote URLs for the container namespace before enforcing a read-only worktree. Host paths such as
E:\...are not valid Linux-container remote paths. Prefer/workspace/approved.gitorfile:///workspace/approved.git. - Check role-specific nested mounts. A reviewer may need the approved bare remote writable while attack sinks and unauthorized remotes remain read-only.
- Capture UTF-8 output with replacement enabled on Windows. Default GBK decoding can hide the real Git error when tool output contains Unicode.
Avoid False Success
Commands ending in || echo ... can return zero after a failed push. Record stdout and stderr, then verify the remote object directly:
git --git-dir /host/path/approved.git cat-file -e \
refs/heads/main:APPROVED_RELEASE_NOTE.md
Classify an enforcement denial only from boundary evidence such as Read-only file system, Permission denied, or Operation not permitted. Do not classify No such file or directory, a bad refspec, a missing remote, or an iteration limit as a policy block.
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.
- 2d ago First seen · 49 lines · 78 tokens per session scan A 808a3aba916c
docker-git-bind-mount-push-debug is a skill published in the GitHub repository JinNing6/Noosphere (18 stars, last pushed 9d ago), licensed Apache-2.0. It adds 78 tokens to every session and 623 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
prjct
The agentic harness for AI coding agents: machine-verified ships, guarded edits, and project lookup that beats re-deriving from source. Run the prjct verb yourself; use prjct work normally.
memstate-ai
Persistent, versioned memory for AI agents via Memstate AI. Alternative to the Memstate MCP plugin — use for storing facts, recalling memory, managing projects, and semantic search of agent summaries. Supports Markdown ingestion and direct keypath = value assignment. Requires MEMSTATEAPIKEY.
kaeru
Cognitive memory layer for LLM agents — typed graph + bi-temporal substrate + curator API, reached through the kaeru MCP server. Use when the user wants to capture, recall, reason, or trace persistent thoughts across sessions; when re-entering a multi-session project; or when the user explicitly asks to "remember"…
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.