> For the complete documentation index, see [llms.txt](https://bso-wiki.oldschool.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bso-wiki.oldschool.gg/custom-items/tames/monkey-staff-and-spells.md). # Monkey Staff & Spells Seamonkey staffs allows your monkey to cast spells You can acquire a t1 staff then upgrade it to higher tiers using the create command `/create item:Seamonkey staff (t1)` ### Seamonkey staff Creation
Staff TierSpeed BoostCostMagic level
T15%1x Polypore staff95
T28%1x Oceanic relic, 1x Seamonkey staff (t1)105
T314%1x Aquifer aegis, 1x Seamonkey staff (t2)115
A tier 2 staff is needed to cast any spell currently. The tier 3 staff boosts your cast time by 12% Feeding your monkey a Klik boosts your Tan leather cast time by a further 22% ### Seamonkey Spells Tame spells are cast with `/tames cast`
SpellCost
Tan LeatherPer 5 casts: 5x Fire rune, 1x Nature rune, 2x Astral rune
Plank MakePer 1 cast: 15x Earth rune, 1x Nature rune, 2x Astral rune, Coins (Regular:70 | Oak:175 | Teak:350 | Mahogany:1,050 | Elder:5950)
Spin flaxPer 5 casts: 5x Flax, 5x Air rune, 1x Nature rune, 2x Astral rune
Superglass makePer 3 casts: 3x Giant seaweed, 18x Bucket of sand, 10x Air rune, 6x Fire rune, 2x Astral rune
--- # 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://bso-wiki.oldschool.gg/custom-items/tames/monkey-staff-and-spells.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.