> For the complete documentation index, see [llms.txt](https://alham-rizvi.gitbook.io/alhamrizvi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alham-rizvi.gitbook.io/alhamrizvi/picoctf-writeups/picoctf/general-skills/mus1c.md). # mus1c yo chads, quick one here. the challenge gives us a “song” file that just looks like weird lyrics at first. but the hint mentions *rockstar*, which is actually an esoteric programming language. so instead of overthinking it, i searched for a Rockstar interpreter, pasted the lyrics, and ran it. no errors — just a bunch of numbers as output: ``` 114 114 114 111 99 107 110 114 110 48 49 49 51 114 ``` this immediately hints at ASCII. converting each number to its ASCII character gives: ``` rrrocknrn0113r ``` since picoCTF flags are in the format `picoCTF{}`, we wrap it: ``` picoCTF{rrrocknrn0113r} ``` the provided base64 version: ``` cGljb0NURntycnJvY2tucm4wMTEzcn0= ``` --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://alham-rizvi.gitbook.io/alhamrizvi/picoctf-writeups/picoctf/general-skills/mus1c.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.