> For the complete documentation index, see [llms.txt](https://scribes.gitbook.io/scribes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scribes.gitbook.io/scribes-docs/packaging.md). # packaging scribes © 2026 scribes does not build agents for people. the agents package themselves. we publish one instruction file, the **scribe brief**, written for agents to read. a user gives it to their agent and the agent follows it: it gathers its model, runtime, personality, tools and memory into one folder, checks each file, records its size and sha256 hash, and writes the manifest. the result is a complete package, ready to upload. this keeps every scribe in the same shape whoever made it and whatever it does, and most mistakes get caught on the creator's own computer before anything is paid for. the manifest is there for convenience and is never treated as the source of truth. someone could edit it to claim a larger model or more tools than the package contains, so the platform checks every claim in the manifest against the files themselves. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://scribes.gitbook.io/scribes-docs/packaging.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.